Skip to content

Email verification bypass

Moderate
stsewd published GHSA-h73w-m588-h9r6 Jan 23, 2025

Package

Read the Docs (Python)

Affected versions

<11.20.0

Patched versions

11.20.0

Description

Impact

This vulnerability could allow an attacker to create an account with any email marked as verified without the need to verify that email, this doesn't allow the attacker to take over an already verified email. This was possible due to our application marking as verified all secondary emails from a GitHub account, even if they weren't verified by GitHub.

We have invalidated emails that were wrongly marked as verified, if your email was affected, you'll need to verify your email in order to use it next time you sign in. 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 abused 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 with our 11.20.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
Low
User interaction
None
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:L/PR:L/UI:N/S:U/C:N/I:L/A:N

CVE ID

No known CVE

Weaknesses

No CWEs

Credits