Skip to content
Fencer Intel
high 7.5

CVE-2012-6661 json

Plone and Zope2 do not reseed pseudo-random number generator

published 2014-11-03 12 y ago modified 2026-06-16 4 mo ago also GHSA-48vv-2pmq-9fvv , PYSEC-2014-51 , PYSEC-2014-76 , EUVD-2014-0069

cvss
7.5
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
2.4%
EPSS 2.4% chance of exploitation in 30 days, percentile 84%
public exploits
0
none known

Summary

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).

Patch / fix

  • pypi zope2 2.13.19
  • pypi plone 4.2.3, 4.3b1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-6661 updated cvss 1.8

(Plone): Python random generator used instead of system random generator

  • Red Hat Enterprise Linux 5 conga
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.38% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • bugs.launchpad.net https://bugs.launchpad.net/zope2/+bug/1071067 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi zope2
<2.13.19
2.13.19
pypi plone
>=3.2.2, <4.2.3
>=4.3a1, <4.3b1
<4.2.3
>=4.3a0, <4.3b1
4.2.3
4.3b1

Classification

Weakness
  • CWE-310 Cryptographic Issues
  • CWE-336 Same Seed in Pseudo-Random Number Generator (PRNG)

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.