Skip to content

Statamic CMS has a Path Traversal in Asset Upload

Moderate severity GitHub Reviewed Published Nov 19, 2024 in statamic/cms • Updated Nov 19, 2024

Package

composer statamic/cms (Composer)

Affected versions

<= 5.16.0

Patched versions

5.17.0

Description

Assets uploaded with appropriately crafted filenames may result in them being placed in a location different than what was configured.

Impact

  • Affects front-end forms with assets fields.
  • Affects other places where assets can be uploaded, although users would need upload permissions anyway.
  • Files can be uploaded so they would be located on the server in a different location, and potentially override existing files.
  • Traversal outside an asset container was not possible.

Patches

This has been fixed in 5.17.0.

References

@jasonvarga jasonvarga published to statamic/cms Nov 19, 2024
Published by the National Vulnerability Database Nov 19, 2024
Published to the GitHub Advisory Database Nov 19, 2024
Reviewed Nov 19, 2024
Last updated Nov 19, 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
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:N/UI:N/S:U/C:N/I:L/A:N

EPSS score

0.045%
(17th percentile)

Weaknesses

CVE ID

CVE-2024-52600

GHSA ID

GHSA-p7f6-8mcm-fwv3

Source code

Credits

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