Skip to content

Project linking to any repository when importing a project via API V3

Moderate
stsewd published GHSA-rmqq-mq6q-8hpg Jul 31, 2024

Package

Read the Docs (Python)

Affected versions

<11.3.1

Patched versions

11.13.1

Description

Impact

This vulnerability could allow an attacker to link a project he controls to any repository (even if the attacker doesn't have access to it) by using the import functionality of API V3. Linking a project to a repository doesn't grant access to the repository or allows changing the repository in any way.

The open source community version of Read the Docs (https://readthedocs.org/) isn't affected by this vulnerability, as the impact is null. While in Read the Docs for Business (https://readthedocs.com) linking a project to a repository can be used to grant a user access to that project controlled by the attacker without the user accepting an invitation, this can be used to carry an attack a similar to GHSA-4mgr-vrh5-hj8q. Note that this doesn't allow the attacker to give himself access to a project.

Users do not need to take any further action, we have taken measures to ensure that the security issue is now fully fixed. 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

This vulnerably doesn't have any impact in the open source version on Read the Docs, so custom installations aren't affected.

Patches

This vulnerability has been patched with our 11.3.1 release.

References

For more information

If you have any questions or comments about this advisory, email us at [email protected] (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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
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:L/UI:N/S:U/C:H/I:N/A:N

CVE ID

No known CVE

Weaknesses

Credits