CVE-2020-10626
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 · uneditedIn Fazecast jSerialComm, Version 2.2.2 and prior, an uncontrolled search path element vulnerability could allow a malicious DLL file with the same name of any resident DLLs inside the software installation to execute arbitrary code.
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 confidenceFazecast jSerialComm version 2.2.2 and prior contains an uncontrolled search path element vulnerability allowing DLL hijacking. The application loads DLLs without specifying full paths, causing the OS to search directories in an order that permits a malicious DLL with the same name as a legitimate resident DLL to be loaded first, leading to arbitrary code execution.
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<= 2.2.2>= 1.5.0.66, <= 1.5.2.28>= 1.6.0.39, <= 1.6.2.14= 1.7.0.64CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
-
Identify jSerialComm installation and versionSearch for jSerialComm JAR files in application directories, Java library folders, or inspect pom.xml/gradle build files for jSerialComm dependency versionAffected if jSerialComm version is 2.2.2 or lower
-
Identify Ecostruxure It Gateway installation and versionLook for Ecostruxure It Gateway in default installation paths such as C:\Program Files\Schneider Electric\EcoStruxure IT Gateway or C:\Program Files (x86)\Schneider Electric\EcoStruxure IT Gateway; check version via installer records, about dialog, or executable propertiesAffected if Ecostruxure It Gateway version is 1.5.0.66 through 1.5.2.28, 1.6.0.39 through 1.6.2.14, or exactly 1.7.0.64
-
Assess DLL search path exposureExamine whether the application runs in a directory or environment where untrusted users can write files; check if the application executable directory or system PATH directories are writable by lower-privileged usersAffected if The application runs from a directory where non-admin users can place files, enabling DLL hijacking
You are affected if either jSerialComm version 2.2.2 or earlier is in use, or Ecostruxure It Gateway version falls within the specified vulnerable ranges, and the application operates in an environment where attackers could inject malicious DLLs into the search path.
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 dataRecompile the application to use secure DLL loading by either bundling required DLLs in the application directory, using absolute paths for DLL loading, or calling SetDllDirectory to set a controlled search path before any DLL operations.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10626 — 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-10626 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