# CVE-2025-0473: Incomplete Cleanup vulnerability in PMB platform

> Attackers can prevent temporary file deletion in PMB platform, leading to disk exhaustion and denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jan 2025
- **Updated:** 16 Jan 2025
- **Also known as:** GHSA-4vfx-xrp7-4c4h

## What is CVE-2025-0473?

CVE-2025-0473 is a medium-severity denial of service vulnerability in PMB platform, published on 16 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability in the PMB platform that allows an attacker to persist temporary files on the server, affecting versions 4.0.10 and above. This vulnerability exists in the file upload functionality on the ‘/pmb/authorities/import/iimport_authorities’ endpoint. When a file is uploaded via this resource, the server will create a temporary file that will be deleted after the client sends a POST request to ‘/pmb/authorities/import/iimport_authorities’. This workflow is automated by the web client, however an attacker can trap and launch the second POST request to prevent the temporary file from being deleted.

Weakness: CWE-459 (Incomplete Cleanup)

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

It affects 1 product.


Products: Sigb Pmb.

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

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

## Is CVE-2025-0473 being exploited?

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

## Other vulnerabilities in PMB platform

- [CVE-2025-0471](https://insights.sbomify.com/CVE-2025-0471/): Unrestricted Upload of File with Dangerous Type vulnerability in PMB platform (critical 9.9)
- [CVE-2025-61168](https://insights.sbomify.com/CVE-2025-61168/): Deserialization in n/a (critical 9.8)
- [CVE-2024-26289](https://insights.sbomify.com/CVE-2024-26289/): Remote Code Inclusion Vulnerability in Multiple PMB Versions (critical 9.8)
- [CVE-2023-37177](https://insights.sbomify.com/CVE-2023-37177/): SQL injection in n/a (critical 9.8)
- [CVE-2023-51828](https://insights.sbomify.com/CVE-2023-51828/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0473 is a medium-severity denial of service vulnerability in PMB platform, published on 16 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0473 in the wild and no public exploit code.

Affected product: PMB platform. 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-0473/ (Markdown: https://insights.sbomify.com/CVE-2025-0473/index.md)
```

## Sources

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

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