Skip to content

Open redirect on docs domains when using exact redirects with `/:splat`

Low
stsewd published GHSA-ggh8-mg84-m86h Jan 23, 2024

Package

Read the Docs (Python)

Affected versions

<=10.16.1

Patched versions

10.17.0

Description

Impact

This vulnerability could potentially allow a malicious user to redirect a user to an external site given a link of the form https://docs.example.com/en/latest/%0D/atacker-site.com/. For this to work, the project must have an exact redirect with /:splat in to_url.

On Read the Docs community (readthedocs.io and custom domains) the impact is almost null, and on Read the Docs for Business (readthedocs-hosted.com and custom domains), it could have been used to intercept a CAS session ticket, this ticket alone can't be used to get a session, the only information that this ticket may provide is the username of the user.

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.

Patches

This vulnerability has been patched in our 10.17.0 release.

References

For more information

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

Severity

Low

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
Unchanged
Confidentiality
None
Integrity
Low
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:U/C:N/I:L/A:N

CVE ID

No known CVE

Weaknesses

Credits