Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 874108 - (CVE-2012-5508, CVE-2012-6661) CVE-2012-5508 CVE-2012-6661 conga (Plone): Python random generator used instead of system random generator
CVE-2012-5508 CVE-2012-6661 conga (Plone): Python random generator used inste...
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20121106,reported=2...
: Security
Depends On: 956861
Blocks: 874222
  Show dependency treegraph
 
Reported: 2012-11-07 09:17 EST by Jan Lieskovsky
Modified: 2014-11-05 09:45 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-06-26 17:13:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Python 16184 None None None Never

  None (edit)
Description Jan Lieskovsky 2012-11-07 09:17:31 EST
It was reported that Plone, a user friendly and powerful content management system based on Zope, used Python language based pseudo-random number generator (PRNG) instead of a system one for generation of pseudo-random numbers. Also, previously, certain Plone error pages leaked random numbers, making it possible for a remote attacker to derive the state of the PRNG in the moment of password reset requests.

References:
[1] http://plone.org/products/plone/security/advisories/20121106/24
[2] http://plone.org/products/plone/security/advisories/20121106/

Relevant upstream HotFixes:
[3] http://plone.org/products/plone-hotfix/releases/20121106
    (django_crypto.py and random_string.py changes seem to be
     relevant for this issue)
Comment 2 Jan Lieskovsky 2012-11-07 11:52:21 EST
From OSS post:
[4] http://www.openwall.com/lists/oss-security/2012/11/07/4

relevant HotFix patch is random_string.py change.
Comment 6 Jan Lieskovsky 2012-11-13 10:34:03 EST
The CVE identifier of CVE-2012-5508 has been assigned to this issue:
http://www.openwall.com/lists/oss-security/2012/11/10/1
Comment 7 Jan Pokorný 2013-06-13 13:24:13 EDT
Reference: https://bugs.launchpad.net/zope2/+bug/1071067
Comment 8 Vincent Danen 2014-06-26 17:13:25 EDT
This issue may affect the version of plone as shipped with EPEL5, however the latest version there is 3.1.6 (and the latest 3.x release is 3.3.5, which was released a year prior to this flaw being discovered).  Given the age of the EPEL5 package and its lack of support, we do not recommend anyone use it.

This issue does not affect plone as provided with the conga package on Red Hat Enterprise Linux 5.

Statement:

Not vulnerable. This issue did not affect the versions of luci (as provided by conga) as shipped with Red Hat Enterprise Linux 5.
Comment 9 Murray McAllister 2014-11-04 00:23:35 EST
A CVE split has occurred:

Common Vulnerabilities and Exposures assigned an identifier CVE-2012-6661 to
the following vulnerability:

Name: CVE-2012-6661
URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-6661
Assigned: 20141103
Reference: http://www.openwall.com/lists/oss-security/2012/11/10/1
Reference: https://bugs.launchpad.net/zope2/+bug/1071067
Reference: https://github.com/plone/Products.CMFPlone/blob/4.2.3/docs/CHANGES.txt
Reference: https://plone.org/products/plone-hotfix/releases/20121124
Reference: https://plone.org/products/plone/security/advisories/20121106/24

Zope before 2.13.19, as used in Plone before 4.2.3 and 4.3 before beta
1, does not reseed the pseudo-random number generator (PRNG), which
makes it easier for remote attackers to guess the value via
unspecified vectors.  NOTE: this issue was SPLIT from CVE-2012-5508 due
to different vulnerability types (ADT2).

Note You need to log in before you can comment on or make changes to this bug.