Summary
DNSJava vulnerable to KeyTrap - Denial-of-Service Algorithmic Complexity Attacks
Workarounds
Although not recommended, only using a non-validating resolver, will remove the vulnerability.
References
Impact
Users using the ValidatingResolver for DNSSEC validation can run into CPU exhaustion with specially crafted DNSSEC-signed zones.
The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.
GHSA-CRJG-W57M-RQQF has a CVSS score of 6.5 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.6.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Users should upgrade to dnsjava v3.6.0
Frequently Asked Questions
- What is GHSA-CRJG-W57M-RQQF? GHSA-CRJG-W57M-RQQF is a high-severity allocation of resources without limits or throttling vulnerability in dnsjava:dnsjava (maven), affecting versions >= 3.5.0, < 3.6.0. It is fixed in 3.6.0. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
- How severe is GHSA-CRJG-W57M-RQQF? GHSA-CRJG-W57M-RQQF has a CVSS score of 6.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by GHSA-CRJG-W57M-RQQF?
dnsjava:dnsjava(maven) (versions >= 3.5.0, < 3.6.0)org.jitsi:dnssecjava(maven) (versions <= 2.0.0)
- Is there a fix for GHSA-CRJG-W57M-RQQF? Yes. GHSA-CRJG-W57M-RQQF is fixed in 3.6.0. Upgrade to this version or later.
- Is GHSA-CRJG-W57M-RQQF exploitable, and should I be worried? Whether GHSA-CRJG-W57M-RQQF is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-CRJG-W57M-RQQF is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-CRJG-W57M-RQQF? Upgrade
dnsjava:dnsjavato 3.6.0 or later.