Skip to content

readthedocs-sphinx-search vulnerable to cross-site scripting when including search results from malicious projects

Moderate severity GitHub Reviewed Published Jan 15, 2024 in readthedocs/readthedocs-sphinx-search

Package

pip readthedocs-sphinx-search (pip)

Affected versions

<= 0.3.1

Patched versions

0.3.2

Description

Impact

This vulnerability could have allowed an attacker to include arbitrary HTML content in search results by having a user search a malicious project. This was due to our search client not correctly escaping all user content from search results. You can find more information in the advisory published in our readthedocs.org repo.

Users of this extension should update to the 0.3.2 version, and trigger a new build.

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

Patches

This issue has been patched in our 0.3.2 version.

References

For more information

If you have any questions or comments about this advisory, email us at [email protected] (PGP)

References

@stsewd stsewd published to readthedocs/readthedocs-sphinx-search Jan 15, 2024
Published to the GitHub Advisory Database Jan 16, 2024
Reviewed Jan 16, 2024

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
Required
Scope
Unchanged
Confidentiality
High
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:R/S:U/C:H/I:L/A:N

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-xgfm-fjx6-62mj

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.