# CVE-2025-1207: phjounin TFTPD64 DNS denial of service

> A local network attacker can cause a denial of service in the TFTPD64 DNS handler, requiring high complexity and local access.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-257h-84mq-c7cf

## What is CVE-2025-1207?

CVE-2025-1207 is a low-severity denial of service vulnerability in phjounin TFTPD64, published on 12 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in phjounin TFTPD64 4.64. It has been declared as problematic. This vulnerability affects unknown code of the component DNS Handler. The manipulation leads to denial of service. The attack needs to be done within the local network. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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


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

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

## Is CVE-2025-1207 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1207 is a low-severity denial of service vulnerability in phjounin TFTPD64, published on 12 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1207 in the wild and no public exploit code.

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

## Sources

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

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