CVE-2012-5485: Code Injection

Published Nov 21, 2012
·
Updated

registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.

Other sources

A security flaw was found in the way Plone, a user friendly and powerful content management system based on Zope, performed execution of restricted Python statements, when the administrator interface / control panel was accessed. A remote attacker could inject specially-crafted Python statement / script into the Plone's restricted Python sandbox that, when the administrator interface was accessed would be executed with the privileges of that admin user.

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

Relevant upstream HotFixes: [3] http://plone.org/products/plone-hotfix/releases/20121106

From the OSS post: [4] http://www.openwall.com/lists/oss-security/2012/11/07/4

the registerConfiglet.py change from upstream HotFix is relevant to this issue.

Red Hat

registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.

MITRE

Affected Software

74 affected componentsFixes available
pip/Plone>=4.3a1<4.3b1
4.3b1
pip/Plone<4.2.3
4.2.3
Plone plone<=4.2.2
Plone plone=1.0
Plone plone=1.0.1
Plone plone=1.0.2
Plone plone=1.0.3
Plone plone=1.0.4
Plone plone=1.0.5
Plone plone=1.0.6
Plone plone=2.0
Plone plone=2.0.1
Plone plone=2.0.2
Plone plone=2.0.3
Plone plone=2.0.4
Plone plone=2.0.5
Plone plone=2.1
Plone plone=2.1.1
Plone plone=2.1.2
Plone plone=2.1.3
Plone plone=2.1.4
Plone plone=2.5
Plone plone=2.5.1
Plone plone=2.5.2
Plone plone=2.5.3
Plone plone=2.5.4
Plone plone=2.5.5
Plone plone=3.0
Plone plone=3.0.1
Plone plone=3.0.2
Plone plone=3.0.3
Plone plone=3.0.4
Plone plone=3.0.5
Plone plone=3.0.6
Plone plone=3.1
Plone plone=3.1.1
Plone plone=3.1.2
Plone plone=3.1.3
Plone plone=3.1.4
Plone plone=3.1.5.1
Plone plone=3.1.6
Plone plone=3.1.7
Plone plone=3.2
Plone plone=3.2.1
Plone plone=3.2.2
Plone plone=3.2.3
Plone plone=3.3
Plone plone=3.3.1
Plone plone=3.3.2
Plone plone=3.3.3
Plone plone=3.3.4
Plone plone=3.3.5
Plone plone=4.0
Plone plone=4.0.1
Plone plone=4.0.2
Plone plone=4.0.3
Plone plone=4.0.4
Plone plone=4.0.5
Plone plone=4.0.6.1
Plone plone=4.1
Plone plone=4.1.4
Plone plone=4.1.5
Plone plone=4.1.6
Plone plone=4.2
Plone plone=4.2-a1
Plone plone=4.2-a2
Plone plone=4.2-b1
Plone plone=4.2-b2
Plone plone=4.2-rc1
Plone plone=4.2-rc2
Plone plone=4.2.0.1
Plone plone=4.2.1
Plone plone=4.2.1.1
Plone plone=4.3

Event History

Nov 21, 2012
Data Sourced
03:08 PM
DescriptionSeverityAffected Software
Sep 30, 2014
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
Data Sourced
via NVD·02:55 PM
RemedyDescriptionSeverityWeaknessAffected Software
May 17, 2022
Advisory Published
04:31 AM

Frequently Asked Questions

1

What is the severity of CVE-2012-5485?

CVE-2012-5485 is considered a critical vulnerability due to its potential to allow remote code execution.

2

How do I fix CVE-2012-5485?

To fix CVE-2012-5485, upgrade Plone to version 4.2.3 or 4.3 beta 1.

3

What versions of Plone are affected by CVE-2012-5485?

Versions of Plone before 4.2.3 and 4.3 up to beta 1 are affected by CVE-2012-5485.

4

What type of vulnerability is CVE-2012-5485?

CVE-2012-5485 is a remote code execution vulnerability.

5

Is CVE-2012-5485 exploitable from the internet?

Yes, CVE-2012-5485 can be exploited remotely, allowing attackers to execute arbitrary Python code through the admin interface.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203