high
7.5
CWE
399 770
Advisory Published
CVE Published
Advisory Published
Updated

CVE-2012-5499

First published: Thu Nov 08 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] <a href="http://plone.org/products/plone/security/advisories/20121106/15">http://plone.org/products/plone/security/advisories/20121106/15</a> [2] <a href="http://plone.org/products/plone/security/advisories/20121106/">http://plone.org/products/plone/security/advisories/20121106/</a> Relevant upstream HotFixes: [3] <a href="http://plone.org/products/plone-hotfix/releases/20121106">http://plone.org/products/plone-hotfix/releases/20121106</a> From the OSS post: [4] <a href="http://www.openwall.com/lists/oss-security/2012/11/07/4">http://www.openwall.com/lists/oss-security/2012/11/07/4</a> the python_scripts.py formatColumns() change from upstream HotFix is relevant to this issue.

Credit: secalert@redhat.com

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

Remedy

https://plone.org/products/plone-hotfix/releases/20121106

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2012-5499?

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

  • How do I fix CVE-2012-5499?

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

  • What systems are affected by CVE-2012-5499?

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

  • Can CVE-2012-5499 be exploited remotely?

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

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

Company

Resources

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203