{"vuid":"VU#725188","idnumber":"725188","name":"ISC BIND 9 vulnerable to denial of service via dynamic update request","keywords":["BIND 9"],"overview":"ISC BIND 9 contains a vulnerability that may allow a remote, unauthenticated attacker to create a denial-of-service condition.","clean_desc":"The Berkeley Internet Name Domain (BIND) is a popular Domain Name System (DNS) implementation from Internet Systems Consortium (ISC). It includes support for dynamic DNS updates as specified in IETF RFC 2136. BIND 9 can crash when processing a specially-crafted dynamic update packet. ISC notes that this vulnerability affects all servers that are masters for one or more zones and is not limited to those that are configured to allow dynamic updates. ISC also indicates that the attack packet has to be constructed for a zone for which the target system is configured as a master; launching the attack against slave zones does not trigger the vulnerability.","impact":"By sending a specially-crafted dynamic update packet to a BIND 9 server, a remote, unauthenticated attacker can cause a denial of service by causing BIND to crash.","resolution":"Apply an update\nUsers who obtain BIND from a third-party vendor, such as their operating system vendor, should see the systems affected portion of this document for a partial list of affected vendors. This vulnerability is addressed in ISC BIND versions 9.4.3-P3, 9.5.1-P3, and BIND 9.6.1-P1. Users of BIND from the original source distribution should upgrade to one of these versions, as appropriate. See also https://www.isc.org/node/474.","workarounds":"","sysaffected":"","thanks":"Thanks to ISC for reporting this vulnerability.","author":"This document was written by Will Dormann and Chad Dougherty.","public":["https://www.isc.org/node/474","http://tools.ietf.org/html/rfc2136","http://oldwww.isc.org/sw/bind/view?release=9.4.3-P3&noframes=1","http://oldwww.isc.org/sw/bind/view?release=9.5.1-P3&noframes=1","http://oldwww.isc.org/sw/bind/view?release=9.6.1-P1&noframes=1","http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538975"],"cveids":["CVE-2009-0696"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2009-07-28T13:22:11Z","publicdate":"2009-07-28T00:00:00Z","datefirstpublished":"2009-07-28T19:02:23Z","dateupdated":"2009-08-27T14:10:50Z","revision":32,"vrda_d1_directreport":"1","vrda_d1_population":"3","vrda_d1_impact":"3","cam_widelyknown":"20","cam_exploitation":"0","cam_internetinfrastructure":"19","cam_population":"15","cam_impact":"8","cam_easeofexploitation":"15","cam_attackeraccessrequired":"20","cam_scorecurrent":"26.325","cam_scorecurrentwidelyknown":"26.325","cam_scorecurrentwidelyknownexploited":"39.825","ipprotocol":"","cvss_accessvector":"","cvss_accesscomplexity":"","cvss_authentication":null,"cvss_confidentialityimpact":"","cvss_integrityimpact":"","cvss_availabilityimpact":"","cvss_exploitablity":null,"cvss_remediationlevel":"","cvss_reportconfidence":"","cvss_collateraldamagepotential":"","cvss_targetdistribution":"","cvss_securityrequirementscr":"","cvss_securityrequirementsir":"","cvss_securityrequirementsar":"","cvss_basescore":"","cvss_basevector":"","cvss_temporalscore":"","cvss_environmentalscore":"","cvss_environmentalvector":"","metric":26.325,"vulnote":null}