Critical Vulnerabilities in Ruby Packages: ruby2.5, ruby2.7, ruby3.0, ruby3.2, ruby3.3
Summary
USN-7734-1: ruby2.5, ruby2.7, ruby3.0, ruby3.2, ruby3.3 vulnerabilities. Affects ruby2.5 versions < 2.5.1-1ubuntu1.16+esm5. Fixed in 2.5.1-1ubuntu1.16+esm5. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Ruby is a dynamic, open-source programming language known for its simplicity and productivity. It supports multiple programming paradigms, including functional and object-oriented programming. The affected packages, ruby2.5, ruby2.7, ruby3.0, ruby3.2, and ruby3.3, are essential for running Ruby applications on Ubuntu systems. These packages provide the Ruby interpreter and development tools necessary for building and executing Ruby programs. However, recent vulnerabilities have been discovered that could compromise the security and stability of applications relying on these versions.
Vulnerability Detail
The vulnerabilities stem from improper handling of IO stream methods, memory operations, XML character parsing, and decompressed domain names within DNS packets. These issues could allow remote attackers to crash Ruby applications, leading to denial of service, or potentially expose sensitive information. Specifically, CVE-2024-27280 and CVE-2024-27282 affect Ruby's handling of IO streams and memory, while CVE-2024-35176 and CVE-2025-24294 relate to XML parsing and DNS packet handling, respectively. Notably, these vulnerabilities primarily impact Ubuntu 18.04 LTS.
How To Fix
Minimum fixed version
2.5.1-1ubuntu1.16+esm5
This is the first release that contains the fix.
sudo apt-get install --only-upgrade ruby2.5
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
If immediate patching is not feasible, consider restricting access to the Ruby applications or services that utilize the affected packages until the vulnerabilities can be addressed. Additionally, monitor application logs for any unusual activity that may indicate an attempted exploit.
Conclusion
In summary, critical vulnerabilities have been identified in several Ruby packages that could lead to significant security risks. It is essential for users to update their packages to the latest patched versions to mitigate these risks. Additionally, utilizing tools like Vulert can help monitor for vulnerabilities in real-time.
See every vulnerability recorded for ruby2.5 →
FAQ
The main vulnerabilities involve improper handling of IO streams, memory operations, XML parsing, and DNS packet handling, which could lead to denial of service or exposure of sensitive information.
The affected versions include ruby2.5, ruby2.7, ruby3.0, ruby3.2, and ruby3.3.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Simply upload your manifest file like package-lock.json to check for vulnerabilities.
Yes, you can restrict access to the affected Ruby applications and monitor logs for unusual activity until the vulnerabilities are patched.
Detailed information can be found in the Ubuntu Security Notices and the CVE listings for each vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for ruby2.5.