Skip to content

aiohttp Cross-site Scripting vulnerability on index pages for static file handling

Moderate severity GitHub Reviewed Published Apr 17, 2024 in aio-libs/aiohttp • Updated May 2, 2024

Package

pip aiohttp (pip)

Affected versions

< 3.9.4

Patched versions

3.9.4

Description

Summary

A XSS vulnerability exists on index pages for static file handling.

Details

When using web.static(..., show_index=True), the resulting index pages do not escape file names.

If users can upload files with arbitrary filenames to the static directory, the server is vulnerable to XSS attacks.

Workaround

We have always recommended using a reverse proxy server (e.g. nginx) for serving static files. Users following the recommendation are unaffected.

Other users can disable show_index if unable to upgrade.

Patch: https://github.com/aio-libs/aiohttp/pull/8319/files

References

@Dreamsorcerer Dreamsorcerer published to aio-libs/aiohttp Apr 17, 2024
Published to the GitHub Advisory Database Apr 18, 2024
Reviewed Apr 18, 2024
Published by the National Vulnerability Database Apr 18, 2024
Last updated May 2, 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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
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:N/UI:R/S:C/C:L/I:L/A:N

EPSS score

0.044%
(12th percentile)

Weaknesses

CVE ID

CVE-2024-27306

GHSA ID

GHSA-7gpw-8wmc-pm8g

Source code

Credits

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