high
7.5
CWE
79
Advisory Published
CVE Published
Advisory Published
Updated

CVE-2012-5486: XSS

First published: Wed Nov 21 2012(Updated: )

A HTTP header injection flaw was found in the way Plone, a user friendly and powerful content management system, performed sanitization of HTTP headers provided within certain URL requests. A remote attacker could provide a specially-crafted URL that, when processed would lead the injected HTTP headers to be returned as part of Plone system HTTP response (possibly leading to HTTP response splitting, cross-site scripting [XSS] flaws, session fixation or unauthorized HTTP redirect attacks - to mention some of the possible negative consequences). References: [1] <a href="http://plone.org/products/plone/security/advisories/20121106/02">http://plone.org/products/plone/security/advisories/20121106/02</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 setHeader.py change from upstream HotFix is relevant to this issue.

Credit: secalert@redhat.com secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
pip/Plone>=4.3a1<=4.3a2
4.3b1
pip/Plone>=3.3.2<4.2.3
4.2.3
pip/Zope2<2.13.19
2.13.19
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
Zope ZODB=2.5.1
Zope ZODB=2.6.1
Zope ZODB=2.6.4
Zope ZODB=2.7.0
Zope ZODB=2.7.3
Zope ZODB=2.7.4
Zope ZODB=2.7.5
Zope ZODB=2.7.6
Zope ZODB=2.7.7
Zope ZODB=2.7.8
Zope ZODB=2.8.1
Zope ZODB=2.8.4
Zope ZODB=2.8.6
Zope ZODB=2.8.8
Zope ZODB=2.9.2
Zope ZODB=2.9.3
Zope ZODB=2.9.4
Zope ZODB=2.9.5
Zope ZODB=2.9.6
Zope ZODB=2.9.7
Zope ZODB=2.10.3
Zope ZODB=2.10.8
Zope ZODB=2.11.0
Zope ZODB=2.11.1
Zope ZODB=2.11.2
Zope ZODB=2.11.3
Zope ZODB=2.13.18

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-5486?

    CVE-2012-5486 has a severity rating of medium due to the potential for HTTP header injection, which could allow attackers to manipulate responses.

  • How do I fix CVE-2012-5486?

    To mitigate CVE-2012-5486, upgrade to the latest versions of Plone or Zope that have addressed this vulnerability.

  • Who is affected by CVE-2012-5486?

    CVE-2012-5486 affects various versions of the Plone content management system and certain Zope versions.

  • What types of attacks can exploit CVE-2012-5486?

    Attackers can exploit CVE-2012-5486 through crafted URLs that inject malicious HTTP headers.

  • Is there a workaround for CVE-2012-5486?

    While upgrading is the best solution, you could potentially restrict access to vulnerable endpoints to mitigate risks while achieving a full upgrade.

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