hickory-net is vulnerable to Improper Verification of Cryptographic Signature
50
Medium Risk
The DNSSEC validation cache keys entries on a 64-bit hash of the owner name, and the name hash ignores label boundaries so names that differ only in dot placement collide. A collision lets a benign insecure verdict for one name be reused for a different target name, so validation is skipped and forged data is returned as an insecure answer (AD=0). The differing hash and equality behavior also enables hash-collision denial of service. The fix makes the name hash and cache key collision-resistant.
You are affected if you are using a version that falls within the vulnerable range and you have DNSSEC validation enabled
hickory-net is vulnerable to Improper Verification of Cryptographic Signature in versions 0.26.0 - 0.26.1.
Upgrade the hickory-net library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.