# CVE-2020-13431: Privilege escalation in n/a

> Local attackers can escalate privileges by replacing the I2PSvc.exe file due to weak directory permissions in the I2P software.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4cfq-849g-j9jx

## What is CVE-2020-13431?

CVE-2020-13431 is a high-severity vulnerability in n/a, published on 16 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

I2P 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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2020-13431?

It affects 1 product.


Products: Geti2p I2p.

## How do I fix CVE-2020-13431?

No fix has been published for CVE-2020-13431 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-13431 being exploited?

There is no known exploitation of CVE-2020-13431 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-13431 and fix it if it is affected.

What it is: CVE-2020-13431 is a high-severity vulnerability in n/a, published on 16 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-13431 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-13431/ (Markdown: https://insights.sbomify.com/CVE-2020-13431/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-13431
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-13431
- OSV: https://osv.dev/vulnerability/CVE-2020-13431

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-13431/
Summaries are generated and may contain mistakes; the official description above is the record.