# CVE-2025-62672: Denial of service in rplay

> Attackers can crash the rplay daemon via crafted packets, causing denial of service without authentication.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Oct 2025
- **Updated:** 20 Oct 2025
- **Also known as:** DEBIAN-CVE-2025-62672, GHSA-4c7m-2jpf-639x, UBUNTU-CVE-2025-62672

## What is CVE-2025-62672?

CVE-2025-62672 is a medium-severity denial of service vulnerability in boyns rplay, published on 19 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

rplay through 3.3.2 allows attackers to cause a denial of service (SIGSEGV and daemon crash) or possibly have unspecified other impact. This occurs in memcpy in the RPLAY_DATA case in rplay_unpack in librplay/rplay.c, potentially reachable via packet data with no authentication.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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


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

Upgrade to a fixed version.

## Is CVE-2025-62672 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-62672 is a medium-severity denial of service vulnerability in boyns rplay, published on 19 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-62672 in the wild and no public exploit code.

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

## Sources

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

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