CVE-2015-7318: Input Validation
First published: Mon Sep 21 2015(Updated: )
A vulnerability was found allowing users who have access to write cookie values were able to inject headers into the response. Versions affected are all versions Plone 3. Upstream hotfix: <a href="https://plone.org/security/20150910/">https://plone.org/security/20150910/</a> CVE request: <a href="http://seclists.org/oss-sec/2015/q3/589">http://seclists.org/oss-sec/2015/q3/589</a>
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| 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 | =3.3.6 | |
| pip/Plone | >=3.3<4.0a1 | 4.0a1 |
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.
Reference Links
- https://nvd.nist.gov/vuln/detail/CVE-2015-7318
- https://bugzilla.redhat.com/show_bug.cgi?id=1264796
- https://plone.org/security/hotfix/20150910/header-injection
- http://www.openwall.com/lists/oss-security/2015/09/22/16
- https://github.com/advisories/GHSA-fq9r-8jpm-2222 (Advisory)
- https://plone.org/security/hotfix/20150910
- https://plone.org/security/20150910/
- http://seclists.org/oss-sec/2015/q3/589
- https://github.com/pypa/advisory-database/tree/main/vulns/plone/PYSEC-2017-54.yaml
Frequently Asked Questions
What is the severity of CVE-2015-7318?
CVE-2015-7318 is considered a moderate severity vulnerability due to its potential for header injection and impact on security.
How do I fix CVE-2015-7318?
To fix CVE-2015-7318, upgrade to Plone version 4.0a1 or later.
What versions of Plone are affected by CVE-2015-7318?
All versions of Plone from 3.3 to 3.3.6 are affected by CVE-2015-7318.
Can CVE-2015-7318 lead to any security risks?
Yes, CVE-2015-7318 can potentially lead to unauthorized header injection that may compromise user sessions.
Is there a workaround for CVE-2015-7318?
There is no official workaround for CVE-2015-7318; the recommended action is to upgrade to a secure version.
- collector/nvd-index
- agent/author
- agent/type
- agent/remedy
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/severity
- agent/description
- agent/event
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2015-7318
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-fq9r-8jpm-2222
- agent/software-canonical-lookup
- agent/references
- agent/last-modified-date
- collector/nvd-cve
- source/NVD
- collector/github-advisory
- agent/softwarecombine
- agent/trending
- agent/tags
- agent/source
- vendor/plone
- canonical/plone plone
- version/plone plone/3.3
- version/plone plone/3.3.1
- version/plone plone/3.3.2
- version/plone plone/3.3.3
- version/plone plone/3.3.4
- version/plone plone/3.3.5
- version/plone plone/3.3.6
- package-manager/pip