CVE-2020-27643
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 · uneditedThe %PROGRAMDATA%\1E\Client directory in 1E Client 5.0.0.745 and 4.1.0.267 allows remote authenticated users and local users to create and modify files in protected directories (where they would not normally have access to create or modify files) via the creation of a junction point to a system directory. This leads to partial privilege escalation.
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 confidenceThe 1E Client installer creates a directory at %PROGRAMDATA%\1E\Client with overly permissive access controls. Authenticated or local users can create filesystem junction points within this directory pointing to protected system locations, allowing them to modify files in directories where they normally lack write permissions. This results in partial privilege escalation.
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= 4.1.0.267= 5.0.0.745CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 1E Client installationCheck for the presence of %PROGRAMDATA%\1E\Client directory or look for 1E Client in Programs and FeaturesAffected if The directory does not exist and 1E Client is not installed, then not affected
-
Determine installed 1E Client versionCheck the version of 1E Client in Programs and Features, or inspect version info in the 1E Client executable if locatedAffected if Installed version matches or falls within the affected version range 4.1.0.267 or 5.0.0.745
-
Confirm vulnerable directory existsVerify %PROGRAMDATA%\1E\Client directory is present on the systemAffected if Directory does not exist, then not vulnerable to this specific flaw
-
Inspect directory permissionsRight-click the %PROGRAMDATA%\1E\Client folder, go to Properties > Security, and examine which users or groups have permissions. Look for permissions that allow Create files / write data or Create folders / append data for authenticated users or low-privilege usersAffected if Authenticated users or non-admin users have permission to create subdirectories or files within this folder, enabling junction point exploitation
The environment is affected if 1E Client version 4.1.0.267 or 5.0.0.745 is installed AND the %PROGRAMDATA%\1E\Client directory exists with permissions allowing low-privilege users to create subdirectories or files.
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 file system permissions on %PROGRAMDATA%\1E\Client to prevent low-privilege users from creating junction points, or apply vendor-provided patches that address the permission misconfiguration in affected versions 5.0.0.745 and 4.1.0.267.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-27643 — 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-2020-27643 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