USN-7366-1: Rack vulnerabilities

Publication date

24 March 2025

Overview

Several security issues were fixed in Rack.


Packages

  • ruby-rack - modular Ruby webserver interface

Details

Nhật Thái Đỗ discovered that Rack incorrectly handled certain usernames. A
remote attacker could possibly use this issue to perform CRLF injection.
(CVE-2025-25184)

Phạm Quang Minh discovered that Rack incorrectly handled certain headers. A
remote attacker could possibly use this issue to perform log injection.
(CVE-2025-27111)

Phạm Quang Minh discovered that Rack did not properly handle relative file
paths. A remote attacker could potentially exploit this to include local
files that should have been inaccessible. (CVE-2025-27610)

Nhật Thái Đỗ discovered that Rack incorrectly handled certain usernames. A
remote attacker could possibly use this issue to perform CRLF injection.
(CVE-2025-25184)

Phạm Quang Minh discovered that Rack incorrectly handled certain headers. A
remote attacker could possibly use this issue to perform log injection.
(CVE-2025-27111)

Phạm Quang Minh discovered that Rack did not properly handle relative file
paths. A remote attacker could potentially exploit this to include local
files that should have been inaccessible. (CVE-2025-27610)

Update instructions

In general, a standard system update will make all the necessary changes.

Learn more about how to get the fixes.

The problem can be corrected by updating your system to the following package versions:

Ubuntu Release Package Version
24.10 oracular ruby-rack –  2.2.7-1.1ubuntu0.1
24.04 noble ruby-rack –  2.2.7-1ubuntu0.2
22.04 jammy ruby-rack –  2.1.4-5ubuntu1.1+esm1  
20.04 focal ruby-rack –  2.0.7-2ubuntu0.1+esm6  
18.04 bionic ruby-rack –  1.6.4-4ubuntu0.2+esm7  
16.04 xenial ruby-rack –  1.6.4-3ubuntu0.2+esm7  
14.04 trusty ruby-rack –  1.5.2-3+deb8u3ubuntu1~esm9  

Reduce your security exposure

Ubuntu Pro provides ten-year security coverage to 25,000+ packages in Main and Universe repositories, and it is free for up to five machines.


Have additional questions?

Talk to a member of the team ›