CVE-2025-27610: Local File Inclusion in Rack::Static
Summary
Rack::Static can serve files under the specified root: even if urls: are provided, which may expose other files under the specified root: unexpectedly.
Details
The vulnerability occurs because Rack::Static does not properly sanitize user-supplied paths before serving files. Specifically, encoded path traversal sequences are not correctly validated, allowing attackers to access files outside the designated static file directory.
Impact
By exploiting this vulnerability, an attacker can gain access to all files under the specified root: directory, provided they are able to determine then path of the file.
Mitigation
- Update to the latest version of Rack, or - Remove usage of Rack::Static, or - Ensure that root: points at a directory path which only contains files which should be accessed publicly.
It is likely that a CDN or similar static file server would also mitigate the issue.
Other sources
Rack provides an interface for developing web applications in Ruby. Prior to versions 2.2.13, 3.0.14, and 3.1.12, Rack::Static can serve files under the specified root: even if urls: are provided, which may expose other files under the specified root: unexpectedly. The vulnerability occurs because Rack::Static does not properly sanitize user-supplied paths before serving files. Specifically, encoded path traversal sequences are not correctly validated, allowing attackers to access files outside the designated static file directory. By exploiting this vulnerability, an attacker can gain access to all files under the specified root: directory, provided they are able to determine then path of the file. Versions 2.2.13, 3.0.14, and 3.1.12 contain a patch for the issue. Other mitigations include removing usage of Rack::Static, or ensuring that root: points at a directory path which only contains files which should be accessed publicly. It is likely that a CDN or similar static file server would also mitigate the issue.
— NVD
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
rubygems/rackto a version that resolves this vulnerability.Fixed in 3.1.12 - Upgrade
Upgrade
rubygems/rackto a version that resolves this vulnerability.Fixed in 3.0.14 - Upgrade
Upgrade
rubygems/rackto a version that resolves this vulnerability.Fixed in 2.2.13 - Upgrade
Upgrade
debian/ruby-rackto a version that resolves this vulnerability.Fixed in 2.1.4-3+deb11u3Fixed in 2.2.13-1~deb12u1Fixed in 3.1.12-1 - Upgrade
Upgrade
Rackto a version that resolves this vulnerability.Fixed in 2.2.13 - Upgrade
Upgrade
Rackto a version that resolves this vulnerability.Fixed in 3.0.14 - Upgrade
Upgrade
Rackto a version that resolves this vulnerability.Fixed in 3.1.12 - Remove
Remove
Rack::Staticfrom your environment.Remove usage of `Rack::Static`.
- Configuration
Ensure the Rack::Static `root:` points to a directory that contains only files that should be accessed publicly.
Rack::Static root: = directory path containing only files intended to be publicly accessible - Compensating control
Use a CDN or similar static file server to mitigate the issue.
Event History
Frequently Asked Questions
What is the severity of CVE-2025-27610?
CVE-2025-27610 has a severity rating that indicates it may expose unintended files, which can lead to information disclosure.
How do I fix CVE-2025-27610?
To fix CVE-2025-27610, upgrade to Rack versions 3.1.12, 3.0.14, or 2.2.13 and ensure proper path sanitization.
What versions of Rack are affected by CVE-2025-27610?
CVE-2025-27610 affects Rack versions prior to 3.1.12, 3.0.14, and all versions before 2.2.13.
What type of vulnerability is CVE-2025-27610?
CVE-2025-27610 is a path traversal vulnerability that arises from improper handling of file paths.
Can CVE-2025-27610 lead to data leakage?
Yes, CVE-2025-27610 can lead to data leakage by exposing files in the specified root that should not be accessible.