10 High
CVSS2
Attack Vector
NETWORK
Attack Complexity
LOW
Authentication
NONE
Confidentiality Impact
COMPLETE
Integrity Impact
COMPLETE
Availability Impact
COMPLETE
AV:N/AC:L/Au:N/C:C/I:C/A:C
0.385 Low
EPSS
Percentile
97.2%
Vulnerabilities in the MIT Kerberos libgssrpc library may allow an attacker to cause a denial of service or potentially execute arbitrary code.
The MIT krb5 Kerberos implementation includes a GSS RPC library used in the Kerberos administration server (kadmind
). Two flaws exist in the libgssprc library that can cause an array overrun if too many file descriptors are opened. These flaws result in a vulnerability that could allow memory corruption in the kadmind
server.
MIT notes that in software versions 1.4 and later, this flaw can only be exploited in configurations that allow large numbers of open file descriptors in a process. In software versions before 1.3, a similar flaw can be exploited in similar circumstances but is further limited to platforms that do not define certain macros in certain C system header files.
An unauthenticated remote attacker can cause memory corruption in the libgssrpc library used by kadmind. ``kadmind
will crash, thereby resulting in a denial of service. MIT notes that it is at least theoretically possible for such corruption to result in database corruption or arbitrary code execution.
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.
Workaround
Before starting kadmind
, use “ulimit -n
” for Bourne shell and derivatives or “limit descriptors
” for C shell and derivatives. Or use similar resource-limiting mechanisms in the invoking process to limit the maximum open file descriptors. The chosen limit should be less than or equal to the value of the FD_SETSIZE
macro typically defined in the <sys/select.h>
header file.
374121
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.
The MIT Kerberos Development Team has published MIT krb5 Security Advisory MITKRB5-SA-2008-002 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%23374121 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%23374121 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 06, 2008
Statement Date: March 06, 2008
Not Affected
No issue with disclosure timelines. 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 06, 2008
Statement Date: March 06, 2008
Not Affected
Status: Not Vulnerable
Vendor Statement:
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 06, 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.
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-002.txt>
Thanks to Ken Raeburn of the MIT Kerberos Team for reporting this vulnerability. MIT credits Jeff Altman of Secure Endpoints with discovering and reporting this issue in software version 1.6.3 and the Red Hat Security Response Team for reporting relevant information about older versions of the software.
This document was written by Chad R Dougherty.
CVE IDs: | CVE-2008-0947, CVE-2008-0948 |
---|---|
Severity Metric: | 2.87 Date Public: |