# CVE-2025-30742: Memory corruption in atophttpd

> An off-by-one error in atophttpd allows out-of-bounds reads, potentially leading to information disclosure or denial of service.

- **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:** No
- **Published:** 26 Mar 2025
- **Updated:** 26 Mar 2025
- **Also known as:** GHSA-q67g-j9gg-987x

## What is CVE-2025-30742?

CVE-2025-30742 is a medium-severity memory corruption vulnerability in pizhenwei atophttpd, published on 26 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

httpd.c in atophttpd 2.8.0 has an off-by-one error and resultant out-of-bounds read because a certain 1024-character req string would not have a final '\0' character.

Weakness: CWE-193 (Off-by-one Error)

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


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

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

## Is CVE-2025-30742 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30742 is a medium-severity memory corruption vulnerability in pizhenwei atophttpd, published on 26 Mar 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-30742 in the wild and no public exploit code.

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

## Sources

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

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