OSV-2025-384 Segv on unknown address in rtpp_refcnt_decref
Not scored
Published
Check this codebase for OSV-2025-384 and fix it if it is affected.
What it is: OSV-2025-384 is a vulnerability in rtpproxy, published on 20 May 2025.
Exploitation: There is no known exploitation of OSV-2025-384 in the wild and no public exploit code.
Affected packages and fixed versions:
- rtpproxy (OSS-Fuzz): affected all versions; no fix listed
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/OSV-2025-384/ (Markdown: https://insights.sbomify.com/OSV-2025-384/index.md)
A segmentation fault in rtpp_refcnt_decref can cause a denial of service in the affected library.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- None listed
What is OSV-2025-384?
OSV-2025-384 is a vulnerability in rtpproxy, published on 20 May 2025.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=418437591
Crash type: Segv on unknown address
Crash state:
rtpp_refcnt_decref
hash_table_purge
rtpp_wref_purge
Which versions are affected by OSV-2025-384?
1 open source package ship an affected version, including rtpproxy.
| Package | Affected | Fixed in |
|---|---|---|
rtpproxy OSS-Fuzz | All versions | None |
How do I fix OSV-2025-384?
No fix has been published for OSV-2025-384 yet. Limit exposure of the affected software until one is available.
Is OSV-2025-384 being exploited?
There is no known exploitation of OSV-2025-384 in the wild and no public exploit code.