CVE-2003-0139
First published: Fri Mar 21 2003(Updated: )
Certain weaknesses in the implementation of version 4 of the Kerberos protocol (krb4) in the krb5 distribution, when triple-DES keys are used to key krb4 services, allow an attacker to create krb4 tickets for unauthorized principals using a cut-and-paste attack and "ticket splicing."
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| MIT Kerberos 5 | =4 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://web.mit.edu/kerberos/www/advisories/MITKRB5-SA-2003-004-krb4.txt
- http://www.kb.cert.org/vuls/id/442569
- http://www.debian.org/security/2003/dsa-266
- http://www.debian.org/security/2003/dsa-273
- http://www.redhat.com/support/errata/RHSA-2003-051.html
- http://www.redhat.com/support/errata/RHSA-2003-052.html
- http://www.redhat.com/support/errata/RHSA-2003-091.html
- http://marc.info/?l=bugtraq&m=104791775804776&w=2
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A250
- http://www.securityfocus.com/archive/1/317130/30/25250/threaded
- http://www.securityfocus.com/archive/1/316960/30/25250/threaded
Frequently Asked Questions
What is the severity of CVE-2003-0139?
CVE-2003-0139 is considered a medium severity vulnerability due to its potential to allow unauthorized access to services.
How do I fix CVE-2003-0139?
To fix CVE-2003-0139, upgrade to a version of MIT Kerberos that does not utilize version 4 of the Kerberos protocol or implement strong security measures to mitigate ticket splicing.
What systems are affected by CVE-2003-0139?
CVE-2003-0139 affects systems running version 4 of the Kerberos protocol in the MIT Kerberos 5 distribution that use triple-DES keys.
What type of attack does CVE-2003-0139 enable?
CVE-2003-0139 enables attacks such as cut-and-paste attacks and ticket splicing, allowing for unauthorized creation of krb4 tickets.
Is CVE-2003-0139 still a relevant concern today?
While CVE-2003-0139 was reported in 2003, systems still using the vulnerable configuration could still be at risk, making it a relevant concern.
- agent/type
- agent/remedy
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/author
- agent/last-modified-date
- agent/weakness
- agent/references
- agent/tags
- agent/description
- agent/first-publish-date
- agent/event
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- vendor/mit
- product/kerberos
- canonical/mit kerberos
- agent/source
- agent/softwarecombine
- canonical/mit kerberos 5
- version/mit kerberos 5/4