DNSJava affected by KeyTrap - NSEC3 closest encloser proof can exhaust CPU resources

published 2024-07-22 2y ago modified 2026-09-10 2mo ago

cvss: 6.5; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

### Impact Users using the `ValidatingResolver` for DNSSEC validation can run into CPU exhaustion with specially crafted DNSSEC-signed zones.

### Patches Users should upgrade to dnsjava v3.6.0

### Workarounds Although not recommended, only using a non-validating resolver, will remove the vulnerability.

### References https://www.athene-center.de/en/keytrap

Patch / fix

fixed in 1 links 1

maven dnsjava:dnsjava 3.6.0

github.com/dnsjava/dnsjava@711af79 commit

Is GHSA-mmwx-rj87-vfgr in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Affected packages

ecosystem	package	affected	fixed in
maven	dnsjava:dnsjava	>=3.5.0, <3.6.0	3.6.0
maven	org.jitsi:dnssecjava	<=2.0.0	no fix listed

Classification

Weakness

CWE-400 Uncontrolled Resource Consumption

References

Sources

GitHub Advisory GHSA-mmwx-rj87-vfgr

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.