CVE-2020-27644
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 Inventory module of the 1E Client 5.0.0.745 doesn't handle an unquoted path when executing %PROGRAMFILES%\1E\Client\Tachyon.Performance.Metrics.exe. This may allow remote authenticated users and local users to gain elevated privileges by placing a malicious cryptbase.dll file in %WINDIR%\Temp\.
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 Inventory module of 1E Client 5.0.0.745 executes Tachyon.Performance.Metrics.exe using an unquoted path. This allows local or remote authenticated attackers to place a malicious cryptbase.dll in %WINDIR%\Temp\, which gets loaded with the elevated privileges of the executing process due to Windows DLL search order behavior.
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= 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Confirm 1E Client installation and versionCheck the installed version of 1E Client by reviewing registry key HKLM\SOFTWARE\1E\Client\CurrentVersion or inspecting the program files directory for 1E Client installationsAffected if The installed version is exactly 5.0.0.745
-
Locate vulnerable executableSearch for Tachyon.Performance.Metrics.exe in the 1E Client installation directory and verify if it uses an unquoted path in any configuration or scheduled taskAffected if Tachyon.Performance.Metrics.exe exists and is invoked via an unquoted path in any execution context
-
Check Inventory module statusReview 1E Client configuration files or registry to determine if the Inventory module is enabledAffected if The Inventory module is enabled and scheduled to run
-
Inspect Temp directory for suspicious DLLsExamine %WINDIR%\Temp\ for any file named cryptbase.dll that was not placed by a trusted processAffected if A cryptbase.dll exists in %WINDIR%\Temp\ and was likely planted
-
Verify process execution contextReview scheduled tasks, service configurations, or startup entries that reference Tachyon.Performance.Metrics.exe to confirm it runs with elevated privilegesAffected if The process runs under elevated or system-level privileges
A user is affected if 1E Client version 5.0.0.745 is installed with the Inventory module enabled and the Tachyon.Performance.Metrics.exe process executes, allowing potential DLL hijacking from %WINDIR%\Temp\.
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 dataApply vendor patch or upgrade to a patched version. As a compensating control, restrict write access to %WINDIR%\Temp\ to prevent DLL planting, though this may have operational impact.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-27644 — 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-27644 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