CVE-2020-5247

Description

In Puma (RubyGem) before 4.3.2 and before 3.12.3, if an application using Puma allows untrusted input in a response header, an attacker can use newline characters (i.e. `CR`, `LF` or`/r`, `/n`) 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-2019-16254, which fixed this vulnerability for the WEBrick Ruby web server. This has been fixed in versions 4.3.2 and 3.12.3 by checking all headers for line endings and rejecting headers with those characters.

Severity
MEDIUM
CVSS v3
6.5
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L · source cna
Exploit chance (EPSS)
2.549%
chance of exploitation in the next 30 days
higher than 85.3% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

Timeline

  1. 2020-02-28Published by the CNA16:55 UTC
  2. 2020-02-28GitHub advisory published (GHSA-84j7-475p-hp8v)same day

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-84j7-475p-hp8v, affected packages:

PackageVulnerable versionsFixed in
RubyGems pumabefore 3.12.43.12.4
RubyGems pumafrom 4.0.0 before 4.3.34.3.3

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
puma pumathrough 3.12.3no fix listedfrom 4.0.0 through 4.3.2no fix listednot listednot listed
ruby-lang rubythrough 2.3.0no fix listedfrom 2.4.0 through 2.4.7no fix listedfrom 2.5.0 through 2.5.6no fix listedfrom 2.6.0 through 2.6.4no fix listed2.7.0no fix listednot listednot listednot listednot listednot listed
debian debian_linux9.0no fix listednot listed
fedoraproject fedora30no fix listed31no fix listed32no fix listednot listednot listednot listed

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources