# CVE-2020-25245: Privilege escalation in DIGSI 4

> An attacker can execute arbitrary code with SYSTEM privileges by placing malicious DLLs in writable directories included in the application's search path.

- **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:** 9 Feb 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3c8w-cf3r-86mw

## What is CVE-2020-25245?

CVE-2020-25245 is a high-severity vulnerability in Siemens DIGSI 4, published on 9 Feb 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been identified in DIGSI 4 (All versions < V4.94 SP1 HF 1). Several folders in the %PATH% are writeable by normal users. As these folders are included in the search for dlls, an attacker could place dlls there with code executed by SYSTEM.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Siemens Digsi 4.

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

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

## Is CVE-2020-25245 being exploited?

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

## Other vulnerabilities in Siemens DIGSI 4

- [CVE-2018-4840](https://insights.sbomify.com/CVE-2018-4840/): Missing authorization in DIGSI 4 (high 7.5)
- [CVE-2018-4839](https://insights.sbomify.com/CVE-2018-4839/): Weak cryptography in DIGSI 4 (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-25245 is a high-severity vulnerability in Siemens DIGSI 4, published on 9 Feb 2021. 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-25245 in the wild and no public exploit code.

Affected product: Siemens DIGSI 4. 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-25245/ (Markdown: https://insights.sbomify.com/CVE-2020-25245/index.md)
```

## Sources

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

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