rack
Affected
- introduced
0, fixed2.2.20(ecosystem)
Fixed versions
2.2.20
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2025-61780
Rack has a Possible Information Disclosure Vulnerability
Summary
A possible information disclosure vulnerability existed in Rack::Sendfile when running behind a proxy that supports x-sendfile headers (such as Nginx). Specially crafted headers could cause Rack::Sendfile to miscommunicate with the proxy and trigger unintended internal requests, potentially bypassing proxy-level access restrictions.
Details
When Rack::Sendfile received untrusted x-sendfile-type or x-accel-mapping headers from a client, it would interpret them as proxy configuration directives. This could cause the middleware to send a "redirect" response to the proxy, prompting it to reissue a new internal request that was not subject to the proxy's access controls.
An attacker could exploit this by:
x-sendfile-type: x-accel-redirect header.x-accel-mapping header.Impact
Attackers could bypass proxy-enforced restrictions and access internal endpoints intended to be protected (such as administrative pages). The vulnerability did not allow arbitrary file reads but could expose sensitive application routes.
This issue only affected systems meeting all of the following conditions:
Rack::Sendfile with a proxy that supports x-accel-redirect (e.g., Nginx).x-sendfile-type and x-accel-mapping headers..to_path.Mitigation
x-accel-redirect: use Rack::Sendfile, "x-accel-redirect"
proxy_set_header x-sendfile-type x-accel-redirect;
proxy_set_header x-accel-mapping /var/www/=/files/;
config.action_dispatch.x_sendfile_header = nilMedium Basis: The source's own band: MODERATE
0, fixed 2.2.20 (ecosystem)2.2.20
The export has no generic command for this ecosystem.
3.0, fixed 3.1.18 (ecosystem)3.1.18
The export has no generic command for this ecosystem.
3.2, fixed 3.2.3 (ecosystem)3.2.3
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0