ID CVE-2012-5507
Summary 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.
References
Vulnerable Configurations
  • cpe:2.3:a:zope:zope:2.13.18
    cpe:2.3:a:zope:zope:2.13.18
  • Zope 2.10.3
    cpe:2.3:a:zope:zope:2.10.3
  • Zope 2.10.8
    cpe:2.3:a:zope:zope:2.10.8
  • Zope 2.11.0
    cpe:2.3:a:zope:zope:2.11.0
  • Zope 2.11.1
    cpe:2.3:a:zope:zope:2.11.1
  • Zope 2.11.2
    cpe:2.3:a:zope:zope:2.11.2
  • Zope 2.11.3
    cpe:2.3:a:zope:zope:2.11.3
  • Zope 2.5.1
    cpe:2.3:a:zope:zope:2.5.1
  • Zope 2.6.1
    cpe:2.3:a:zope:zope:2.6.1
  • Zope 2.6.4
    cpe:2.3:a:zope:zope:2.6.4
  • Zope 2.7.0
    cpe:2.3:a:zope:zope:2.7.0
  • Zope 2.7.3
    cpe:2.3:a:zope:zope:2.7.3
  • Zope 2.7.4
    cpe:2.3:a:zope:zope:2.7.4
  • Zope 2.7.5
    cpe:2.3:a:zope:zope:2.7.5
  • Zope 2.7.6
    cpe:2.3:a:zope:zope:2.7.6
  • Zope 2.7.7
    cpe:2.3:a:zope:zope:2.7.7
  • Zope 2.7.8
    cpe:2.3:a:zope:zope:2.7.8
  • Zope 2.8.1
    cpe:2.3:a:zope:zope:2.8.1
  • Zope 2.8.4
    cpe:2.3:a:zope:zope:2.8.4
  • Zope 2.8.6
    cpe:2.3:a:zope:zope:2.8.6
  • Zope 2.8.8
    cpe:2.3:a:zope:zope:2.8.8
  • Zope 2.9.2
    cpe:2.3:a:zope:zope:2.9.2
  • Zope 2.9.3
    cpe:2.3:a:zope:zope:2.9.3
  • Zope 2.9.4
    cpe:2.3:a:zope:zope:2.9.4
  • Zope 2.9.5
    cpe:2.3:a:zope:zope:2.9.5
  • Zope 2.9.6
    cpe:2.3:a:zope:zope:2.9.6
  • Zope 2.9.7
    cpe:2.3:a:zope:zope:2.9.7
  • Plone 4.3
    cpe:2.3:a:plone:plone:4.3
  • Plone 4.2.2
    cpe:2.3:a:plone:plone:4.2.2
  • Plone 4.2.1
    cpe:2.3:a:plone:plone:4.2.1
  • cpe:2.3:a:plone:plone:4.2.1.1
    cpe:2.3:a:plone:plone:4.2.1.1
  • cpe:2.3:a:plone:plone:4.2.0.1
    cpe:2.3:a:plone:plone:4.2.0.1
  • Plone 4.2
    cpe:2.3:a:plone:plone:4.2
  • cpe:2.3:a:plone:plone:4.2:rc2
    cpe:2.3:a:plone:plone:4.2:rc2
  • cpe:2.3:a:plone:plone:4.2:rc1
    cpe:2.3:a:plone:plone:4.2:rc1
  • cpe:2.3:a:plone:plone:4.2:b2
    cpe:2.3:a:plone:plone:4.2:b2
  • cpe:2.3:a:plone:plone:4.2:b1
    cpe:2.3:a:plone:plone:4.2:b1
  • cpe:2.3:a:plone:plone:4.2:a2
    cpe:2.3:a:plone:plone:4.2:a2
  • cpe:2.3:a:plone:plone:4.2:a1
    cpe:2.3:a:plone:plone:4.2:a1
  • Plone 4.1.6
    cpe:2.3:a:plone:plone:4.1.6
  • Plone 4.1.5
    cpe:2.3:a:plone:plone:4.1.5
  • Plone 4.1.4
    cpe:2.3:a:plone:plone:4.1.4
  • Plone 4.1
    cpe:2.3:a:plone:plone:4.1
  • Plone 4.0.6.1
    cpe:2.3:a:plone:plone:4.0.6.1
  • Plone 4.0.5
    cpe:2.3:a:plone:plone:4.0.5
  • Plone 4.0.4
    cpe:2.3:a:plone:plone:4.0.4
  • Plone 4.0.3
    cpe:2.3:a:plone:plone:4.0.3
  • Plone 4.0.2
    cpe:2.3:a:plone:plone:4.0.2
  • Plone 4.0.1
    cpe:2.3:a:plone:plone:4.0.1
  • Plone 4.0
    cpe:2.3:a:plone:plone:4.0
  • Plone 3.3.5
    cpe:2.3:a:plone:plone:3.3.5
  • Plone 3.3.4
    cpe:2.3:a:plone:plone:3.3.4
  • Plone 3.3.3
    cpe:2.3:a:plone:plone:3.3.3
  • Plone 3.3.2
    cpe:2.3:a:plone:plone:3.3.2
  • Plone 3.3.1
    cpe:2.3:a:plone:plone:3.3.1
  • Plone 3.3
    cpe:2.3:a:plone:plone:3.3
  • Plone 3.2.3
    cpe:2.3:a:plone:plone:3.2.3
  • Plone 3.2.2
    cpe:2.3:a:plone:plone:3.2.2
  • Plone 3.2.1
    cpe:2.3:a:plone:plone:3.2.1
  • Plone 3.2
    cpe:2.3:a:plone:plone:3.2
  • Plone 3.1.7
    cpe:2.3:a:plone:plone:3.1.7
  • Plone 3.1.6
    cpe:2.3:a:plone:plone:3.1.6
  • Plone 3.1.5.1
    cpe:2.3:a:plone:plone:3.1.5.1
  • Plone 3.1.4
    cpe:2.3:a:plone:plone:3.1.4
  • Plone 3.1.3
    cpe:2.3:a:plone:plone:3.1.3
  • Plone 3.1.2
    cpe:2.3:a:plone:plone:3.1.2
  • Plone 3.1.1
    cpe:2.3:a:plone:plone:3.1.1
  • Plone 3.1
    cpe:2.3:a:plone:plone:3.1
  • Plone 3.0.6
    cpe:2.3:a:plone:plone:3.0.6
  • Plone 3.0.5
    cpe:2.3:a:plone:plone:3.0.5
  • Plone 3.0.4
    cpe:2.3:a:plone:plone:3.0.4
  • Plone 3.0.3
    cpe:2.3:a:plone:plone:3.0.3
  • Plone 3.0.2
    cpe:2.3:a:plone:plone:3.0.2
  • Plone 3.0.1
    cpe:2.3:a:plone:plone:3.0.1
  • Plone 3.0
    cpe:2.3:a:plone:plone:3.0
  • Plone 2.5.5
    cpe:2.3:a:plone:plone:2.5.5
  • Plone 2.5.4
    cpe:2.3:a:plone:plone:2.5.4
  • Plone 2.5.3
    cpe:2.3:a:plone:plone:2.5.3
  • Plone 2.5.2
    cpe:2.3:a:plone:plone:2.5.2
  • Plone 2.5.1
    cpe:2.3:a:plone:plone:2.5.1
  • Plone 2.5
    cpe:2.3:a:plone:plone:2.5
  • Plone 2.1.4
    cpe:2.3:a:plone:plone:2.1.4
  • Plone 2.1.3
    cpe:2.3:a:plone:plone:2.1.3
  • Plone 2.1.2
    cpe:2.3:a:plone:plone:2.1.2
  • Plone 2.1.1
    cpe:2.3:a:plone:plone:2.1.1
  • Plone 2.1
    cpe:2.3:a:plone:plone:2.1
  • Plone 2.0.5
    cpe:2.3:a:plone:plone:2.0.5
  • Plone 2.0.4
    cpe:2.3:a:plone:plone:2.0.4
  • Plone 2.0.3
    cpe:2.3:a:plone:plone:2.0.3
  • Plone 2.0.2
    cpe:2.3:a:plone:plone:2.0.2
  • Plone 2.0.1
    cpe:2.3:a:plone:plone:2.0.1
  • Plone 2.0
    cpe:2.3:a:plone:plone:2.0
  • Plone 1.0.6
    cpe:2.3:a:plone:plone:1.0.6
  • Plone 1.0.5
    cpe:2.3:a:plone:plone:1.0.5
  • Plone 1.0.4
    cpe:2.3:a:plone:plone:1.0.4
  • Plone 1.0.3
    cpe:2.3:a:plone:plone:1.0.3
  • Plone 1.0.2
    cpe:2.3:a:plone:plone:1.0.2
  • Plone 1.0.1
    cpe:2.3:a:plone:plone:1.0.1
  • Plone 1.0
    cpe:2.3:a:plone:plone:1.0
CVSS
Base: 4.3 (as of 01-10-2014 - 23:03)
Impact:
Exploitability:
CWE CWE-362
CAPEC
  • Leveraging Race Conditions
    This attack targets a race condition occurring when multiple processes access and manipulate the same resource concurrently and the outcome of the execution depends on the particular order in which the access takes place. The attacker can leverage a race condition by "running the race", modifying the resource and modifying the normal execution flow. For instance a race condition can occur while accessing a file, the attacker can trick the system by replacing the original file with his version and cause the system to read the malicious file.
  • Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions
    This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. The typical example is the file access. The attacker can leverage a file access race condition by "running the race", meaning that he would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the attacker could do something such as replace the file and cause an escalation of privilege.
Access
VectorComplexityAuthentication
NETWORK MEDIUM NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL NONE NONE
refmap via4
confirm
mlist [oss-security] 20121109 Re: Re: CVE Request - Zope / Plone: Multiple vectors corrected within 20121106 fix
Last major update 02-10-2014 - 14:25
Published 30-09-2014 - 10:55
Back to Top