# CVE-2025-61430: Information disclosure in n/a

> A remote attacker can view other clients' DNS queries due to improper TCP length handling in Simple DNS Plus.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Oct 2025
- **Updated:** 24 Oct 2025
- **Also known as:** GHSA-9qfx-2rgm-h5rf

## What is CVE-2025-61430?

CVE-2025-61430 is a medium-severity vulnerability in n/a, published on 24 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper handling of DNS over TCP in Simple DNS Plus v9 allows a remote attacker with querying access to the DNS server to cause the server to return request payloads from other clients. This happens when the TCP length prefix is malformed (len differs from actual packet len), and due to a concurrency/buffering issue, even when the lengths match. A length prefix that is smaller than the actual packet size increases information leakage. In summary, this vulnerability allows an attacker to see DNS queries of other clients.

Weakness: CWE-350 (Reliance on Reverse DNS Resolution for a Security-Critical Action)

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


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

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

## Is CVE-2025-61430 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61430 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61430 is a medium-severity vulnerability in n/a, published on 24 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61430 exists.

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

## Sources

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

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