CVE-2007-2930: The (1) NSID_SHUFFLE_ONLY and (2) NSID_USE_POOL PRNG algorithms in ISC BIND 8 before 8.4.7-P1 generate pred...

Security readout for executives and security teams

This old BIND 8 flaw can make DNS transaction IDs predictable for some outgoing queries. If an exposed resolver still runs vulnerable BIND 8, an attacker may be able to poison DNS cache entries and redirect users or systems to wrong destinations. Exposure is most likely in legacy DNS infrastructure, appliances, or vendor products still embedding BIND 8. Modern supported BIND deployments are unlikely to be affected, but old Unix, telecom, or security appliances should be checked. Treat as a legacy infrastructure risk. It is not flagged as actively exploited in the provided sources, but exposed vulnerable resolvers can undermine trust in DNS-dependent business systems. Prioritize discovery and retirement of BIND 8. Mitigation focus: Inventory DNS servers and appliances for ISC BIND 8 usage.; Upgrade BIND 8 before 8.4.7-P1 to a fixed or supported version.; Use vendor advisories for packaged products from Avaya, Sun, Nortel, or HP..

Prepared

Jun 29, 2026, 03:38 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.