CVE-2020-5249
Last modified
CVE-2020-5249 is a medium-severity vulnerability rated 6.5/10 on the CVSS scale. In Puma (RubyGem) before 4.3.3 and 3.12.4, if an application using Puma allows untrusted input in an early-hints header, an attacker can use a carriage return character to end the header and inject malicious content, such as additional headers or an entirely new response body. This vulnerability is known as HTTP Response Splitting. EPSS estimates a 1.57% chance of exploitation in the next 30 days.
Description
In Puma (RubyGem) before 4.3.3 and 3.12.4, if an application using Puma allows untrusted input in an early-hints header, an attacker can use a carriage return character to end the header and inject malicious content, such as additional headers or an entirely new response body. This vulnerability is known as HTTP Response Splitting. While not an attack in itself, response splitting is a vector for several other attacks, such as cross-site scripting (XSS). This is related to CVE-2020-5247, which fixed this vulnerability but only for regular responses. This has been fixed in 4.3.3 and 3.12.4.
Metrics
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Puma | Puma | <= 3.12.3 |
| Puma | Puma | >= 4.0.0, <= 4.3.2 |
References
- https://github.com/puma/puma/commit/c22712fc93284a45a93f9ad7023888f3a65524f3Patch, Third Party Advisory
- https://github.com/puma/puma/security/advisories/GHSA-33vf-4xgg-9r58Third Party Advisory
- https://github.com/puma/puma/security/advisories/GHSA-84j7-475p-hp8vThird Party Advisory
- https://owasp.org/www-community/attacks/HTTP_Response_SplittingThird Party Advisory
- https://github.com/puma/puma/commit/c22712fc93284a45a93f9ad7023888f3a65524f3Patch, Third Party Advisory
- https://github.com/puma/puma/security/advisories/GHSA-33vf-4xgg-9r58Third Party Advisory
- https://github.com/puma/puma/security/advisories/GHSA-84j7-475p-hp8vThird Party Advisory
- https://owasp.org/www-community/attacks/HTTP_Response_SplittingThird Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2020-5249?
How severe is CVE-2020-5249?
How do I fix CVE-2020-5249?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2020
- CVE-2020-5243uap-core before 0.7.3 is vulnerable to a denial of service a…7.5
- CVE-2020-5244In BuddyPress before 5.1.2, requests to a certain REST API e…7.5
- CVE-2020-5245Dropwizard-Validation before 1.3.19, and 2.0.2 may allow arb…8.8
- CVE-2020-5246Traccar GPS Tracking System before version 4.9 has a LDAP in…6.5
- CVE-2020-5247In Puma (RubyGem) before 4.3.2 and before 3.12.3, if an appl…7.5
- CVE-2020-5248GLPI before before version 9.4.6 has a vulnerability involvi…5.3
- CVE-2020-5250In PrestaShop before version 1.7.6.4, when a customer edits …6.3
- CVE-2020-5251In parser-server before version 4.1.0, you can fetch all the…5.3
- CVE-2020-5252The command-line "safety" package for Python has a potential…4.1
- CVE-2020-5253NetHack before version 3.6.0 allowed malicious use of escapi…9.8
- CVE-2020-5254In NetHack before 3.6.6, some out-of-bound values for the hi…8.1
- CVE-2020-5255In Symfony before versions 4.4.7 and 5.0.7, when a `Response…4.3
Are you affected by CVE-2020-5249?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
