CVE-2012-5507: Plone and Zope2 affected by Race Condition

CVE-2012-5507 · Severity: low · CVSS 3.1 · Published 2014-09-30

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.

Technologies: plone (PyPI), Zope2 (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2012-5507 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2012-5507 being exploited in the wild.
How severe is CVE-2012-5507?
Low severity, with a CVSS score of 3.1, published 30 September 2014.
Which products and versions are affected?
plone (PyPI) ECOSYSTEM:introduced=0,fixed=4.2.3,introduced=4.3a0,fixed=4.3b1, ECOSYSTEM:introduced=3.2.2,fixed=4.2.3; Zope2 (PyPI) ECOSYSTEM:introduced=0,fixed=2.13.19.
Is there a fix for CVE-2012-5507?
Yes. plone (PyPI): upgrade to 4.2.3, 4.3b1 or later; Zope2 (PyPI): upgrade to 2.13.19 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2012-5507?
Check whether you run plone (PyPI) or Zope2 (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • plone (PyPI): upgrade to 4.2.3, 4.3b1 or later
    pip install "plone>=4.3b1"
  • Zope2 (PyPI): upgrade to 2.13.19 or later
    pip install "Zope2>=2.13.19"

Affected products

  • plone (PyPI) ECOSYSTEM:introduced=0,fixed=4.2.3,introduced=4.3a0,fixed=4.3b1, ECOSYSTEM:introduced=3.2.2,fixed=4.2.3
  • Zope2 (PyPI) ECOSYSTEM:introduced=0,fixed=2.13.19

Identifiers

  • CVE-2012-5507
  • GHSA-3qpr-7rmg-73v8
  • PYSEC-2014-49
  • PYSEC-2014-75

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.