CVE-2012-5499: High severity plone cms vulnerability

Published Nov 8, 2012
·
Updated

A denial of service flaw was found in the way Plone, a user friendly and powerful content management system, performed processing of very large values passed to an internal utility function being exposed on an URL. A remote attacker could provide a specially-crafted URL that, when processed would lead to excessive memory consumption.

References: [1] http://plone.org/products/plone/security/advisories/20121106/15 [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 pythonscripts.py formatColumns() change from upstream HotFix is relevant to this issue.

Other sources

pythonscripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to cause a denial of service (memory consumption) via a large value, related to formatColumns.

GitHub

pythonscripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to cause a denial of service (memory consumption) via a large value, related to formatColumns.

MITRE

Affected Software

74 affected componentsFixes available
pip/Plone>=4.3a1<4.3b1
4.3b1
pip/Plone>=4.0<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 8, 2012
Data Sourced
03:33 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-5499?

CVE-2012-5499 has been classified as a denial of service vulnerability.

2

How do I fix CVE-2012-5499?

To mitigate CVE-2012-5499, upgrade Plone to versions 4.3b1 or 4.2.3 or later.

3

What systems are affected by CVE-2012-5499?

CVE-2012-5499 affects various versions of Plone prior to 4.3b1 and 4.2.3.

4

Can CVE-2012-5499 be exploited remotely?

Yes, a remote attacker can exploit CVE-2012-5499 by sending specially crafted requests.

5

What kind of attacks can CVE-2012-5499 lead to?

CVE-2012-5499 can lead to a denial of service condition in affected Plone systems.

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