CVE-2012-5507

Plone and Zope2 affected by Race Condition

AccessControl/AuthEncoding.py in Zope before 2.13.19, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote attackers to obtain passwords via vectors involving timing discrepancies in password validation.

Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing. Typical impact: TOCTOU exploits, data corruption, or privilege escalation.

CVE-2012-5507 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.13.19, 4.2.3, 4.3b1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2012-5507? CVE-2012-5507 is a high-severity race condition vulnerability in Zope2 (pip), affecting versions < 2.13.19. It is fixed in 2.13.19, 4.2.3, 4.3b1. Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing.
2. How severe is CVE-2012-5507? CVE-2012-5507 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2012-5507?
   • Zope2 (pip) (versions < 2.13.19)
   • Plone (pip) (versions >= 3.2.2, < 4.2.3)
4. Is there a fix for CVE-2012-5507? Yes. CVE-2012-5507 is fixed in 2.13.19, 4.2.3, 4.3b1. Upgrade to this version or later.
5. Is CVE-2012-5507 exploitable, and should I be worried? Whether CVE-2012-5507 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
6. What actually determines whether CVE-2012-5507 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.
7. How do I fix CVE-2012-5507?
   • Upgrade Zope2 to 2.13.19 or later
   • Upgrade Plone to 4.2.3 or later
   • Upgrade Plone to 4.3b1 or later

Other vulnerabilities in Zope2