{"answers":{"affected":"8 open source packages ship an affected version, including plone, Plone and Zope2. It affects 2 products.","exploited":"There is no known exploitation of CVE-2012-6661 in the wild and no public exploit code.","fix":"Upgrade plone to a fixed version for your release line: 4.2.3 or 4.3b1.","what":"CVE-2012-6661 is a medium-severity vulnerability in Plone Plone, published on 3 Nov 2014. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2012-6661 and fix it if it is affected.\n\nWhat it is: CVE-2012-6661 is a medium-severity vulnerability in Plone Plone, published on 3 Nov 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2012-6661 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- plone (PyPI): affected all versions; fixed in 4.2.3, 4.3b1\n- plone (PyPI): affected from 3.2.2; fixed in 4.2.3\n- plone (PyPI): affected from 4.3a1; fixed in 4.3b1\n- Plone (PyPI): affected from 3.2.2; fixed in 4.2.3\n- Plone (PyPI): affected from 4.3a1; fixed in 4.3b1\n- Zope2 (PyPI): affected all versions; fixed in 2.13.19\n- zope2 (PyPI): affected all versions; fixed in 2.13.19\n- zope2 (PyPI): affected all versions; fixed in 2.13.19\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2012-6661/ (Markdown: https://insights.sbomify.com/CVE-2012-6661/index.md)","id":"CVE-2012-6661","markdown":"https://insights.sbomify.com/CVE-2012-6661/index.md","name":"CVE-2012-6661","record":{"aliases":["GHSA-48vv-2pmq-9fvv","PYSEC-2014-51","PYSEC-2014-76"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Zope web framework","requires_auth":"none","summary":"Remote attackers can guess pseudo-random values due to lack of PRNG reseeding, potentially bypassing security controls in Zope and Plone.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"plone","vendor":"plone"},{"product":"zope","vendor":"zope"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-310","name":null}],"description":"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).","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Plone and Zope2 do not reseed pseudo-random number generator","id":"CVE-2012-6661","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"plone:plone","products":["plone:plone"],"type":"weak_cryptography","year":"2012"},"n_packages":8,"n_references":5,"next":{"headline":"jquery-ui Tooltip widget vulnerable to XSS","id":"CVE-2012-6662"},"packages":[{"ecosystem":"PyPI","fixed":["4.2.3"],"introduced":["3.2.2"],"last_affected":[],"package":"Plone","purl":null,"source":"GHSA-48vv-2pmq-9fvv"},{"ecosystem":"PyPI","fixed":["4.3b1"],"introduced":["4.3a1"],"last_affected":[],"package":"Plone","purl":null,"source":"GHSA-48vv-2pmq-9fvv"},{"ecosystem":"PyPI","fixed":["2.13.19"],"introduced":["0"],"last_affected":[],"package":"Zope2","purl":null,"source":"GHSA-48vv-2pmq-9fvv"},{"ecosystem":"PyPI","fixed":["4.2.3","4.3b1"],"introduced":["0","4.3a0"],"last_affected":[],"package":"plone","purl":"pkg:pypi/plone","source":"PYSEC-2014-51"},{"ecosystem":"PyPI","fixed":["4.2.3"],"introduced":["3.2.2"],"last_affected":[],"package":"plone","purl":"pkg:pypi/plone","source":"GHSA-48vv-2pmq-9fvv"},{"ecosystem":"PyPI","fixed":["4.3b1"],"introduced":["4.3a1"],"last_affected":[],"package":"plone","purl":"pkg:pypi/plone","source":"GHSA-48vv-2pmq-9fvv"},{"ecosystem":"PyPI","fixed":["2.13.19"],"introduced":["0"],"last_affected":[],"package":"zope2","purl":"pkg:pypi/zope2","source":"GHSA-48vv-2pmq-9fvv"},{"ecosystem":"PyPI","fixed":["2.13.19"],"introduced":["0"],"last_affected":[],"package":"zope2","purl":"pkg:pypi/zope2","source":"PYSEC-2014-76"}],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2012-6660"},"products":["n/a"],"published":"2014-11-03","related":[{"cvss_score":9.9,"headline":"Incorrect Permission Assignment for Critical Resource in Plone","id":"CVE-2021-33509","kev_date_added":null,"published":"2021-05-21"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-35190","kev_date_added":null,"published":"2020-12-17"},{"cvss_score":9.8,"headline":"Plone Unauthenticated Write Vulnerability","id":"CVE-2020-7941","kev_date_added":null,"published":"2020-01-23"},{"cvss_score":9.3,"headline":"Zope Command Execution Vulnerability","id":"CVE-2011-3587","kev_date_added":null,"published":"2011-10-10"},{"cvss_score":8.8,"headline":"Server-Side Request Forgery in Plone CMS","id":"CVE-2021-33926","kev_date_added":null,"published":"2023-02-17"},{"cvss_score":8.8,"headline":"Improper Restriction of XML External Entity Reference in Plone","id":"CVE-2020-28734","kev_date_added":null,"published":"2020-12-30"},{"cvss_score":8.8,"headline":"SSRF attacks via tracebacks in Plone","id":"CVE-2020-28735","kev_date_added":null,"published":"2020-12-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["n/a"]},"summary":"Remote attackers can guess pseudo-random values due to lack of PRNG reseeding, potentially bypassing security controls in Zope and Plone.","url":"https://insights.sbomify.com/CVE-2012-6661/"}