Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-v7pc-74h8-xq2h

Hickory DNS failure to verify self-signed RRSIG for DNSKEYs

No CVSS score

Published by the GitHub Advisory Database at 10 Feb 2025, 21:52 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
hickory-protocrates.io>=0.8.0, <0.24.3 || >=0.25.0-alpha.1, <0.25.0-alpha.50.24.3, 0.25.0-alpha.5
Identifiers
GHSA-v7pc-74h8-xq2h · RUSTSEC-2025-0006
Weakness (CWE)
CWE-345
Tags
Published
10 Feb 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Hickory DNS (hickory-proto crate) versions from 0.8.0 before 0.24.3, and 0.25.0-alpha.1 before 0.25.0-alpha.5, fail to properly verify DNSKEY record sets during DNSSEC validation. When one DNSKEY in a zone matches a trust anchor or is covered by a DS record, the other keys in that zone are trusted without their own signatures being checked, so an attacker controlling a zone could have forged records accepted as authenticated. Upgrade hickory-proto to 0.24.3, 0.25.0-alpha.5, or later. The source gives few details on exploitation conditions.

Written 8 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

No source has published a CVSS score for this record yet.

  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 15:17 UTC First seen by agentprime
  2. 31 Oct 2026, 15:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.