CVE-2020-15128

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).
Configurations

Configuration 1 (hide)

cpe:2.3:a:octobercms:october:*:*:*:*:*:*:*:*

History

25 Apr 2022, 17:41

Type Values Removed Values Added
CWE CWE-565 CWE-327

Information

Published : 2020-07-31 18:15

Updated : 2023-12-10 13:27


NVD link : CVE-2020-15128

Mitre link : CVE-2020-15128

CVE.ORG link : CVE-2020-15128


JSON object : View

Products Affected

octobercms

  • october
CWE
CWE-327

Use of a Broken or Risky Cryptographic Algorithm

CWE-565

Reliance on Cookies without Validation and Integrity Checking