# CVE-2020-15128: Reliance on Cookies without validation in OctoberCMS

> Attackers can bypass cookie validation by reusing encrypted values across different cookie names, potentially forcing decryption of sensitive data.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 31 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-55mm-5399-7r63

## What is CVE-2020-15128?

CVE-2020-15128 is a medium-severity vulnerability in Octobercms October, published on 31 Jul 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm), CWE-565 (Reliance on Cookies without Validation and Integrity Checking)

## Which versions are affected by CVE-2020-15128?

2 open source packages ship an affected version, including october/rain. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `october/rain` | Packagist | From 1.0.319 | 1.0.468 |
| `october/rain` | Packagist | From 1.0.319 | 1.0.468 |

Products: Octobercms October.

## How do I fix CVE-2020-15128?

Upgrade october/rain to 1.0.468 or later.

## Is CVE-2020-15128 being exploited?

There is no known exploitation of CVE-2020-15128 in the wild and no public exploit code.

## Other vulnerabilities in Octobercms October

- [CVE-2021-32648](https://insights.sbomify.com/CVE-2021-32648/): October CMS Improper Authentication (high 8.2, exploited in the wild)
- [CVE-2021-3311](https://insights.sbomify.com/CVE-2021-3311/): October CMS Session ID not invalidated after logout (critical 9.8)
- [CVE-2017-1000194](https://insights.sbomify.com/CVE-2017-1000194/): October CMS File Upload Vulnerability (critical 9.8)
- [CVE-2017-1000196](https://insights.sbomify.com/CVE-2017-1000196/): Code injection in n/a (critical 9.8)
- [CVE-2017-1000197](https://insights.sbomify.com/CVE-2017-1000197/): Path traversal in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-15128 and fix it if it is affected.

What it is: CVE-2020-15128 is a medium-severity vulnerability in Octobercms October, published on 31 Jul 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-15128 in the wild and no public exploit code.

Affected packages and fixed versions:
- october/rain (Packagist): affected from 1.0.319; fixed in 1.0.468
- october/rain (Packagist): affected from 1.0.319; fixed in 1.0.468

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-15128/ (Markdown: https://insights.sbomify.com/CVE-2020-15128/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-15128
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-15128
- OSV: https://osv.dev/vulnerability/CVE-2020-15128

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-15128/
Summaries are generated and may contain mistakes; the official description above is the record.