# CVE-2025-0542: G DATA Management Server Local privilege escalation

> Local attackers can escalate privileges to SYSTEM by placing a crafted ZIP archive in a writable directory, leading to arbitrary file writes.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 25 Jan 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-4482-3c55-4652

## What is CVE-2025-0542?

CVE-2025-0542 is a high-severity vulnerability in G DATA Management Server, published on 25 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Local privilege escalation due to incorrect assignment of privileges of temporary files in the update mechanism of G DATA Management Server. This vulnerability allows a local, unprivileged attacker to escalate privileges on affected installations by placing a crafted ZIP archive in a globally writable directory, which gets unpacked in the context of SYSTEM and results in arbitrary file write.

Weakness: CWE-276 (Incorrect Default Permissions), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-0542?


## How do I fix CVE-2025-0542?

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

## Is CVE-2025-0542 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0542 and fix it if it is affected.

What it is: CVE-2025-0542 is a high-severity vulnerability in G DATA Management Server, published on 25 Jan 2025. 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-2025-0542 in the wild and no public exploit code.

Affected product: G DATA Management Server. 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-2025-0542/ (Markdown: https://insights.sbomify.com/CVE-2025-0542/index.md)
```

## Sources

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

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