Summary
The HTTP Digest Access Authentication implementation in Apache Tomcat 5.5.x before 5.5.36, 6.x before 6.0.36, and 7.x before 7.0.30 caches information about the authenticated user within the session state, which makes it easier for remote attackers to bypass authentication via vectors related to the session ID.
Impact
The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
org.apache.tomcat:tomcat-catalina to 5.5.36 or later; org.apache.tomcat:tomcat-catalina to 6.0.36 or later; org.apache.tomcat:tomcat-catalina to 7.0.30 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2012-5886? CVE-2012-5886 is a medium-severity improper authentication vulnerability in org.apache.tomcat:tomcat-catalina (maven), affecting versions >= 5.5.0, < 5.5.36. It is fixed in 5.5.36, 6.0.36, 7.0.30. The application does not adequately verify the identity of a user, device, or process before granting access.
- Which versions of org.apache.tomcat:tomcat-catalina are affected by CVE-2012-5886? org.apache.tomcat:tomcat-catalina (maven) versions >= 5.5.0, < 5.5.36 is affected.
- Is there a fix for CVE-2012-5886? Yes. CVE-2012-5886 is fixed in 5.5.36, 6.0.36, 7.0.30. Upgrade to this version or later.
- Is CVE-2012-5886 exploitable, and should I be worried? Whether CVE-2012-5886 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2012-5886 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2012-5886?
- Upgrade
org.apache.tomcat:tomcat-catalinato 5.5.36 or later - Upgrade
org.apache.tomcat:tomcat-catalinato 6.0.36 or later - Upgrade
org.apache.tomcat:tomcat-catalinato 7.0.30 or later
- Upgrade