Skip to content

Reliance on Cookies without validation in OctoberCMS

Moderate severity GitHub Reviewed Published Jul 30, 2020 in octobercms/october • Updated Feb 1, 2023

Package

composer october/rain (Composer)

Affected versions

>= 1.0.319, < 1.0.468

Patched versions

1.0.468

Description

Impact

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

Patches

Issue has been patched in Build 468 (v1.0.468).

NOTE: If you are using the cookie session driver, all of your session data will be invalidated. All other session drivers should smoothly upgrade to the changes (although the backend authentication persist cookie will also be invalidated requiring users to login again once their current session expires).

Workarounds

Apply octobercms/library@28310d4 to your installation manually if unable to upgrade to Build 468.

References

For more information

If you have any questions or comments about this advisory:

Threat Assessment

Assessed as Low given that it is not directly exploitable within the core but requires other security vulnerabilities within the application to have an effect and the severity of its effect depends entirely on the severity of those other holes in the application's defences.

Acknowledgements

Thanks to Takashi Terada of Mitsui Bussan Secure Directions, Inc. for finding the original issue in Laravel and @taylorotwell for sharing the report with the October CMS team.

References

@LukeTowers LukeTowers published to octobercms/october Jul 30, 2020
Reviewed Jul 31, 2020
Published by the National Vulnerability Database Jul 31, 2020
Published to the GitHub Advisory Database Aug 5, 2020
Last updated Feb 1, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:H/A:N

EPSS score

0.060%
(27th percentile)

CVE ID

CVE-2020-15128

GHSA ID

GHSA-55mm-5399-7r63

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.