Skip to content

Sprockets path traversal leads to information leak

High severity GitHub Reviewed Published Jun 20, 2018 to the GitHub Advisory Database • Updated Sep 5, 2023

Package

bundler sprockets (RubyGems)

Affected versions

< 2.12.5
>= 3.0.0, < 3.7.2
>= 4.0.0.beta1, <= 4.0.0.beta7

Patched versions

2.12.5
3.7.2
4.0.0.beta8

Description

Specially crafted requests can be used to access files that exist on the filesystem that is outside an application's root directory, when the Sprockets server is used in production.

All users running an affected release should either upgrade or use one of the work arounds immediately.

Workaround:

In Rails applications, work around this issue, set config.assets.compile = false and config.public_file_server.enabled = true in an initializer and precompile the assets.

This work around will not be possible in all hosting environments and upgrading is advised.

References

Published to the GitHub Advisory Database Jun 20, 2018
Reviewed Jun 16, 2020
Last updated Sep 5, 2023

Severity

High

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
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.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

2.274%
(90th percentile)

Weaknesses

CVE ID

CVE-2018-3760

GHSA ID

GHSA-pr3h-jjhj-573x

Source code

Credits

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