First published: Fri Jul 31 2020(Updated: )
In OctoberCMS before version 1.0.468, encrypted cookie values were not tied to the name of the cookie the value belonged to. This meant that certain classes of attacks that took advantage of other theoretical vulnerabilities in user facing code (nothing exploitable in the core project itself) had a higher chance of succeeding. Specifically, if your usage exposed a way for users to provide unfiltered user input and have it returned to them as an encrypted cookie (ex. storing a user provided search query in a cookie) they could then use the generated cookie in place of other more tightly controlled cookies; or if your usage exposed the plaintext version of an encrypted cookie at any point to the user they could theoretically provide encrypted content from your application back to it as an encrypted cookie and force the framework to decrypt it for them. Issue has been fixed in build 468 (v1.0.468).
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Octobercms October | <1.0.468 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-15128 is a vulnerability in OctoberCMS before version 1.0.468 where encrypted cookie values were not tied to the name of the cookie.
The severity of CVE-2020-15128 is medium with a CVSS score of 6.3.
CVE-2020-15128 affects OctoberCMS before version 1.0.468, allowing certain classes of attacks that take advantage of other theoretical vulnerabilities in user-facing code.
To fix CVE-2020-15128 in OctoberCMS, upgrade to version 1.0.468 or later.
Yes, you can find more information about CVE-2020-15128 on the GitHub commits and security advisories provided in the references section.