CVE-2006-0527

Description

References

• attrition.org/pipermail/vim/2006-February/000551.html
• computerworld.com/networkingtopics/networking/story/0%2C10801%2C103744%2C00.html
• secunia.com/advisories/18690 · Patch
• securityreason.com/securityalert/438
• securityreason.com/securityalert/748
• securitytracker.com/id · Patch
• securitytracker.com/id · Patch
• osvdb.org/22888
• securityfocus.com/archive/1/425083/100/0/threaded
• securityfocus.com/bid/16455
• vupen.com/english/advisories/2006/0399 · Vendor Advisory
• www1.itrc.hp.com/service/cki/docDisplay.do
• exchange.xforce.ibmcloud.com/vulnerabilities/24414

Weitere Schwachstellen in bind

• CVE-2026-13321HOCH 8.6The BIND resolver accepts validly-signed NSEC records where the "Next Domain Name" field points outside the signer's zone. This issue affect…
• CVE-2026-13204HOCH 7.5If a provably insecure domain is covered by both an NSEC and NSEC3 record at the parent, and there exist an RRSIG for only one of these type…
• CVE-2026-12617HOCH 7.5The issue is unexpected program termination based on ordering and/or specific content in responses to queries for CNAME or DNAME, and A reco…
• CVE-2026-11721HOCH 7.5It is possible for an attacker's zone to respond to a query with an RRSIG that has a smaller number of labels than the zone in which the RRS…
• CVE-2026-11622HOCH 7.5A DNSSEC validating resolver that is under a random subdomain attack against a DNSSEC-signed zone can suffer from runaway memory usage. The …