{"vuid":"VU#16532","idnumber":"16532","name":"BIND T_NXT record processing may cause buffer overflow","keywords":["BIND","dns","ns_resp.c","Next record","NXT","T_NXT","dlen","MAXDATA*2","buffer overflow"],"overview":"A vulnerability in BIND, repaired in verison 8.2.2p5, allows remote attackers to execute code with the privileges of the process running named. This vulnerability was widely exploited from November 1999 to December 2000.","clean_desc":"There is  a buffer overflow in the processing of NXT records in the routine rrextract, part of the file ns_resp.c. Specifically, in vulnerable versions of BIND, there is a section of code which reads: case T_NXT: n = dn_expand(msg, eom, cp, (char *)data, sizeof data); if (n < 0) {\n                        hp->rcode = FORMERR; return (-1); if (!ns_nameok((char *)data, class, NULL, response_trans,\n                               domain_ctx, dname, from.sin_addr)) {\n                        hp->rcode = FORMERR; return (-1); cp += n; cp1 = data + strlen((char *)data) + 1; memcpy(cp1, cp, dlen - n); The value of the dlen can be influenced by an intruder in such a way that the expression 'dlen - n' is larger than the size allocated to cp1. Further, the contents of cp can be influenced by an intruder. Thus, this vulnerability can be exploited to execute arbitrary code with the privileges of the process running named. An exploit for this vulnerability is publicly available . NXT record processing was introduced to BIND in version 8.2. 8.1.2 and earlier (including 4.9.x) do not appear to be vulnerable to this problem.","impact":"Remote user may gain default process access of local nameserver, usually root","resolution":"Upgrade to the latest version of BIND.","workarounds":"","sysaffected":"","thanks":"Our thanks to ISC for assistance in understanding this vulnerability.","author":"This document was written by Shawn V Hernan.","public":["http://www.isc.org/products/BIND/bind-security-19991108.html","http://www.redhat.com/support/errata/RHSA1999054-01.html","http://www.debian.org/security/1999/19991116","ftp://ftp.sco.com/SSE/sse033.ltr","http://www.securityfocus.com/vdb/bottom.html?vid=788"],"cveids":["CVE-1999-0833"],"certadvisory":"CA-1999-14","uscerttechnicalalert":null,"datecreated":"2000-07-18T15:38:47Z","publicdate":"1999-11-10T00:00:00Z","datefirstpublished":"2001-01-28T22:09:57Z","dateupdated":"2006-02-03T22:28:59Z","revision":7,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"20","cam_exploitation":"8","cam_internetinfrastructure":"19","cam_population":"19","cam_impact":"19","cam_easeofexploitation":"17","cam_attackeraccessrequired":"20","cam_scorecurrent":"108.164625","cam_scorecurrentwidelyknown":"108.164625","cam_scorecurrentwidelyknownexploited":"135.781125","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":108.164625,"vulnote":null}