{"vuid":"VU#895609","idnumber":"895609","name":"MIT Kerberos krb4-enabled KDC contains multiple vulnerabilities","keywords":["MIT","Kerberos 5","krb4-enabled KDC","DoS","denial of service","information disclosure","arbitrary code execution"],"overview":"Vulnerabilities in the MIT Kerberos Key Distribution Center server could allow a remote attacker to compromise the key database, gain access to sensitive information, or cause a denial of service.","clean_desc":"Several vulnerabilities exist in the Authentication Service and Key Distribution Center server (krb5kdc) included in the MIT krb5 Kerberos implementation. In one case, the use of a null or dangling pointer in the KDC can result in a crash or double-free, and may leak portions of process memory to an attacker. In another case, uninitialized stack values cause reuse of a small window of previous stack values to be interpreted as message content. Some of this content may be returned to the attacker as part of an error response. These vulnerabilities are only exposed if Kerberos 4 support is enabled. MIT notes that by default, Kerberos 4 support is compiled in but not enabled in recent versions of the software. MIT also notes that no other client or application server programs are affected.","impact":"An unauthenticated remote attacker may cause a krb4-enabled KDC server to crash, expose information (potentially including secret key data), or execute arbitrary code with the privileges of the krb5kdc. Secondary impacts include compromise of the Kerberos key database and denial of service to clients attempting to authenticate in the affected Kerberos realm.","resolution":"Upgrade or apply a patch from the vendor Patches have been released to address these issues. Please see the Systems Affected section of this document for more details.","workarounds":"","sysaffected":"","thanks":"Thanks to Ken Raeburn of the MIT Kerberos Team for reporting this vulnerability.","author":"This document was written by Chad R Dougherty.","public":["h","t","t","p",":","/","/","w","e","b",".","m","i","t",".","e","d","u","/","k","e","r","b","e","r","o","s","/","a","d","v","i","s","o","r","i","e","s","/","M","I","T","K","R","B","5","-","S","A","-","2","0","0","8","-","0","0","1",".","t","x","t"],"cveids":["CVE-2008-0062","CVE-2008-0063"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2008-03-05T15:53:11Z","publicdate":"2008-03-18T00:00:00Z","datefirstpublished":"2008-03-19T02:56:46Z","dateupdated":"2011-07-22T12:52:32Z","revision":14,"vrda_d1_directreport":"1","vrda_d1_population":"3","vrda_d1_impact":"3","cam_widelyknown":"15","cam_exploitation":"0","cam_internetinfrastructure":"12","cam_population":"10","cam_impact":"19","cam_easeofexploitation":"7","cam_attackeraccessrequired":"15","cam_scorecurrent":"10.0996875","cam_scorecurrentwidelyknown":"11.97","cam_scorecurrentwidelyknownexploited":"19.45125","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":10.0996875,"vulnote":null}