CVE-2024-1343
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA weak permission was found in the backup directory in LaborOfficeFree affecting version 19.10. This vulnerability allows any authenticated user to read backup files in the directory '%programfiles(x86)% LaborOfficeFree BackUp'.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceLaborOfficeFree version 19.10 has improper access controls on its backup directory at '%programfiles(x86)%\LaborOfficeFree\BackUp'. The directory permissions allow any authenticated user to read backup files, enabling potential exposure of sensitive data contained in those backups.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 19.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify LaborOfficeFree version 19.10 is installedCheck the installed version of LaborOfficeFree in Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or look at the program's properties in Add/Remove Programs. Alternatively, right-click the executable and view its version info.Affected if The installed version is exactly 19.10 (the only affected version listed)
-
Confirm backup directory existsNavigate to %programfiles(x86)%\LaborOfficeFree\BackUp or use Command Prompt: dir "%programfiles(x86%)\LaborOfficeFree\BackUp"Affected if The BackUp folder exists at the specified path
-
Examine backup directory permissionsRight-click the BackUp folder, select Properties, then go to the Security tab. Review the list of users and groups with Read permissions.Affected if Authenticated Users, Users group, or other non-admin accounts have Read or List permissions to the folder
-
Test if regular users can access backup filesUse icacls command: icacls "%programfiles(x86)%\LaborOfficeFree\BackUp\*" to see which users can read files. Alternatively, attempt access using a non-admin account or run PowerShell Get-Acl on the folder as a standard user.Affected if Non-administrator accounts are granted Read access to files in the BackUp folder
-
Check for sensitive data in backupsList contents of the BackUp directory using dir command and note file types. If readable, attempt to open a backup file to verify it contains sensitive data such as credentials, employee records, or configuration data.Affected if Backup files are readable by standard users AND contain sensitive information
A user is affected if LaborOfficeFree version 19.10 is installed and the BackUp directory grants Read access to authenticated non-administrator users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict read permissions on the backup directory to only Administrators and SYSTEM account; verify that regular authenticated users cannot enumerate or read files in the BackUp folder.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1343 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-1343 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data