En resumen
- CVE-2025-61780 es una vulnerabilidad MEDIO (CVSS 5.3) que afecta a rack, rack (rack).
- Probabilidad de explotación en los próximos 30 días (EPSS): 0.55%, mayor que el 46.2% de las vulnerabilidades.
- Solución: actualizar a 3.1.18, 3.2.3, 2.2.20 o posterior.
| Package | Affected versions | Patched versions |
|---|
| rack RubyGems | ≥ 3.0, < 3.1.18≥ 3.2, < 3.2.3< 2.2.20
| 3.1.183.2.32.2.20
|
| rack | ≥ 3.0.0, < 3.1.18≥ 3.2.0, < 3.2.3< 2.2.20
| 3.1.183.2.32.2.20
|
Description
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:
- Setting a crafted
x-sendfile-type: x-accel-redirect header.
- Setting a crafted
x-accel-mapping header.
- Requesting a path that qualifies for proxy-based acceleration.
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:
- The application used
Rack::Sendfile with a proxy that supports x-accel-redirect (e.g., Nginx).
- The proxy did not always set or remove the
x-sendfile-type and x-accel-mapping headers.
- The application exposed an endpoint that returned a body responding to
.to_path.
Mitigation
-
Upgrade to a fixed version of Rack which requires explicit configuration to enable x-accel-redirect:
use Rack::Sendfile, "x-accel-redirect"
-
Alternatively, configure the proxy to always set or strip the headers (you should be doing this!):
proxy_set_header x-sendfile-type x-accel-redirect;
proxy_set_header x-accel-mapping /var/www/=/files/;
-
Or in Rails applications, disable sendfile completely:
config.action_dispatch.x_sendfile_header = nil
NVD description
Rack is a modular Ruby web server interface. Prior to versions 2.2.20, 3.1.18, and 3.2.3, 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. 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 setting a crafted `x-sendfile-type: x-accel-redirect` header, setting a crafted `x-accel-mapping` header, and requesting a path that qualifies for proxy-based acceleration. 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: The application used `Rack::Sendfile` with a proxy that supports `x-accel-redirect` (e.g., Nginx); the proxy did **not** always set or remove the `x-sendfile-type` and `x-accel-mapping` headers; and the application exposed an endpoint that returned a body responding to `.to_path`. Users should upgrade to Rack versions 2.2.20, 3.1.18, or 3.2.3, which require explicit configuration to enable `x-accel-redirect`. Alternatively, configure the proxy to always set or strip the header, or in Rails applications, disable sendfile completely.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free