CVE-2020-13431
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 · uneditedI2P before 0.9.46 allows local users to gain privileges via a Trojan horse I2PSvc.exe file because of weak permissions on a certain %PROGRAMFILES% subdirectory.
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 confidenceI2P before version 0.9.46 contains a local privilege escalation vulnerability due to weak file permissions on a subdirectory within %PROGRAMFILES% where the I2PSvc.exe service executable resides. An unprivileged local user can replace or insert a malicious Trojan horse I2PSvc.exe file in this weakly-protected directory, which will be executed with elevated privileges when the service runs.
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< 0.9.46CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Verify I2P installation existsCheck for I2P installation directory, typically in %PROGRAMFILES%\i2p or %PROGRAMFILES(X86)%\i2p, and confirm I2PSvc.exe file is presentAffected if I2PSvc.exe is found in a subdirectory under %PROGRAMFILES% with weak permissions
-
Identify installed I2P versionCheck the version of I2PSvc.exe or look for a version file in the I2P installation directory; compare against the affected range (versions before 0.9.46)Affected if Installed version is less than 0.9.46
-
Inspect permissions on the I2PSvc.exe directoryUse icacls or PowerShell Get-Acl to examine the ACLs on the directory containing I2PSvc.exe; check if Users orAuthenticated Users have Write or Modify permissionsAffected if Non-privileged users (such as Users group or Authenticated Users) have Write or Modify permissions on the directory containing I2PSvc.exe
-
Verify service configurationCheck if I2P service is registered using sc query I2PService or by inspecting the service in services.msc; note the executable pathAffected if I2P service is installed and configured to run I2PSvc.exe from the weakly-protected directory
You are affected if I2P version is below 0.9.46 AND the directory containing I2PSvc.exe grants write access to non-privileged users, allowing potential privilege escalation via service execution.
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 data0.9.46
Upgrade to I2P version 0.9.46 or later, which contains the fix for the weak permissions vulnerability. Alternatively, manually harden file permissions on the affected directory to restrict write access to privileged users only.
- Consultation1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13431 — 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-13431 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