9.3 High
CVSS2
Attack Vector
NETWORK
Attack Complexity
MEDIUM
Authentication
NONE
Confidentiality Impact
COMPLETE
Integrity Impact
COMPLETE
Availability Impact
COMPLETE
AV:N/AC:M/Au:N/C:C/I:C/A:C
9.8 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
0.602 Medium
EPSS
Percentile
97.8%
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.
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.
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.
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.
895609
Filter by status: All Affected Not Affected Unknown
Filter by content: __ Additional information available
__ Sort by: Status Alphabetical
Expand all
Javascript is disabled. Click here to view vendors.
Notified: March 06, 2008 Updated: March 18, 2008
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Apple has published Apple Security Update 2008-002 to address these vulnerabilities. Users are encouraged to review this update and apply the patches it refers to.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23895609 Feedback>).
Notified: March 06, 2008 Updated: March 18, 2008
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
The MIT Kerberos Development Team has published MIT krb5 Security Advisory MITKRB5-SA-2008-001 in response to this issue. Users are encouraged to review this advisory and apply the appropriate patch or workaround.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23895609 Feedback>).
Notified: March 06, 2008 Updated: March 19, 2008
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Ubuntu has published Ubuntu Security Notice USN-587 in response to this issue. Users are encouraged to review this notice and apply the updates it refers to.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23895609 Feedback>).
Notified: March 06, 2008 Updated: March 10, 2008
Statement Date: March 10, 2008
Not Affected
PSIRT confirms our products that run MIT Kerberos are not affected by these vulnerabilities.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 18, 2008
Statement Date: March 15, 2008
Not Affected
FYI - no CA products ship or statically link with Kerberos libraries, so we do not consider any CA products to be vulnerable.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: July 22, 2011
Not Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 10, 2008
Statement Date: March 06, 2008
Not Affected
Checked internally and Intel is not using MIT Kerberos in our product mix.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 10, 2008
Statement Date: March 06, 2008
Not Affected
Intoto products are not affected due to the potential exploits documented in this vulnerability note, because they do not use MIT Kerberos implementation.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: April 03, 2008
Statement Date: March 19, 2008
Not Affected
Juniper Networks products are not susceptible to this vulnerability.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: April 03, 2008
Statement Date: March 20, 2008
Not Affected
Please update your advisory to indicate that Microsoft is not vulnerable.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 10, 2008
Statement Date: March 06, 2008
Not Affected
No Secure Computing products make use of MIT Kerberos.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 18, 2008
Statement Date: March 11, 2008
Not Affected
Sun's Kerberos implementation is not impacted by these issues so you can mark us down as 'Not Impacted'. CERT VU#895609 corresponds to krb4 which we don't support and we managed to address CERT VU#374121 in a different bug fix years ago.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 18, 2008
Statement Date: March 11, 2008
Not Affected
TippingPoint does not use the Kerberos implementation its products.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: March 06, 2008 Updated: March 06, 2008
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
View all 82 vendors __View less vendors __
Group | Score | Vector |
---|---|---|
Base | ||
Temporal | ||
Environmental |
<http://web.mit.edu/kerberos/advisories/MITKRB5-SA-2008-001.txt>
Thanks to Ken Raeburn of the MIT Kerberos Team for reporting this vulnerability.
This document was written by Chad R Dougherty.
CVE IDs: | CVE-2008-0062, CVE-2008-0063 |
---|---|
Severity Metric: | 10.10 Date Public: |
9.3 High
CVSS2
Attack Vector
NETWORK
Attack Complexity
MEDIUM
Authentication
NONE
Confidentiality Impact
COMPLETE
Integrity Impact
COMPLETE
Availability Impact
COMPLETE
AV:N/AC:M/Au:N/C:C/I:C/A:C
9.8 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
0.602 Medium
EPSS
Percentile
97.8%