Sprockets path traversal leads to information leak
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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2018-3760US | high7.5 | Exploit | ||
There is an information leak vulnerability in Sprockets. Versions Affected: 4.0.0.beta7 and lower, 3.7.1 and lower, 2.12.4 and lower. Specially crafted requests can be used to acce… | ||||
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2018:2244WEB
- https://access.redhat.com/errata/RHSA-2018:2245WEB
- https://access.redhat.com/errata/RHSA-2018:2561WEB
- https://access.redhat.com/errata/RHSA-2018:2745WEB
- https://github.com/rails/sprocketsPACKAGE
- https://github.com/rails/sprockets/commit/18b8a7f07a50c245e9aee7854ecdbe606bbd8bb5WEB
- https://github.com/rails/sprockets/commit/9c34fa05900b968d74f08ccf40917848a7be9441WEB
- https://github.com/rails/sprockets/commit/c09131cf5b2c479263939c8582e22b98ed616c5fWEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan