Skip to content

Cache poisoning

Moderate
ericholscher published GHSA-7fcx-wwr3-99jv Jan 16, 2023

Package

Read the Docs (Python)

Affected versions

<=9.1.2

Patched versions

9.2.0

Description

Impact

This vulnerability could potentially allow a malicious user to get some private information about a user account like: username, name, and audit logs.

Exploiting this would have required an attacker to get a logged-in user to visit a malicious URL, after visiting that URL, the content of that page would have been cached for all users in our CDN, allowing the attacker to retrieve that private content.
This URL would have looked something like https://readthedocs.org/accounts/security-log/ext.js, where ext.js could have been any path ending with any of the extensions from https://developers.cloudflare.com/cache/about/default-cache-behavior/#default-cached-file-extensions.

This vulnerability requires the use of a CDN to be exploited, so it was present in our https://readthedocs.org site only, https://readthedocs.com doesn't make use of a CDN, so it wasn't affected. Users of https://readthedocs.org/ do not need to take any further action, we have taken measures to ensure that the security issue is now fully fixed. Our CDN doesn't cache cookies, so user's sessions are safe.

This issue was discovered by a member of our team, and we have seen no signs that this vulnerability was exploited in the wild.

Custom installations

We don't officially support custom installations of Read the Docs, but If you are using a custom installation, we recommend you to upgrade. If you are using a CDN that automatically caches resources based on its extension, you are probably affected by this vulnerability, and if your CDN caches cookies, your user's sessions could have been compromised.

Patches

This vulnerability has been patched in our 9.2.0 release.

References

For more information

If you have any questions or comments about this advisory, email us at security@readthedocs.org (PGP)

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
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
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:L/PR:N/UI:R/S:U/C:L/I:N/A:N

CVE ID

No known CVE

Weaknesses

Credits