Skip to content
Fencer Intel
medium 6.5

CVE-2020-5247 json

HTTP Response Splitting in Puma

published 6y ago modified 2mo ago also BIT-ruby-2020-5247 , BIT-ruby-min-2020-5247 , EUVD-2020-0295 , GHSA-84j7-475p-hp8v

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.5%
EPSS 2.5% chance of exploitation in 30 days, percentile 85%
public exploits
0
none known

Summary

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.

Patch / fix

  • rubygems puma 3.12.4, 4.3.3
  • bitnami ruby 2.3.1, 2.4.8, 2.5.7, 2.6.5
  • bitnami ruby-min 2.3.1, 2.4.8, 2.5.7, 2.6.5
  • puma Debian 14, Debian 13, Debian 12 3.12.4-1

debian advisories DEBIAN-CVE-2020-5247

  • rmt-server SLE Module for Server Applications 15 SP1, SLE Module for Public Cloud 15 SP1 2.6.5-3.18.1
  • rmt-server SLES for SAP 15, SLES 15-LTSS, SLE High Performance Computing 15-LTSS +1 more 2.6.5-3.34.1
  • rmt-server SLE Module for Server Applications 15 SP2, SLE Module for Public Cloud 15 SP2 2.6.5-3.3.1
  • kibana OpenStack Cloud 7 4.6.3-5.1
  • ansible OpenStack Cloud 7 2.2.3.0-12.2
  • grafana OpenStack Cloud 7 4.6.5-1.14.1
  • memcached OpenStack Cloud 7 1.5.17-3.6.1
  • python-py OpenStack Cloud 7 1.8.1-11.12.1

suse advisories SUSE-SU-2020:3160-1SUSE-SU-2020:3147-1SUSE-SU-2020:3036-1SUSE-RU-2020:2072-1SUSE-SU-2020:2060-1SUSE-SU-2020:1190-1

  • rmt-server openSUSE Leap 15.1 2.6.5-lp151.2.18.2
  • rmt-server openSUSE Leap 15.2 2.6.5-lp152.2.3.1

opensuse advisories openSUSE-SU-2020:2000-1openSUSE-SU-2020:1993-1

Is CVE-2020-5247 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-5247 updated cvss 0.0

rubygem-puma: attacker is able to use newline characters to insert malicious content (HTTP Response Splitting), this could lead to XSS

  • Red Hat CloudForms Management Engine 5 rubygem-puma
    affected: no fix planned “Will not fix”
  • Red Hat 3scale API Management Platform 2 system
    affected: no fix available
  • Red Hat Software Collections rh-ror50-rubygem-puma Red Hat Storage 3 rubygem-puma
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.55% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
rubygems puma
<3.12.4
>=4.0.0, <4.3.3
3.12.4
4.3.3
bitnami ruby
<2.3.1
>=2.4.0, <2.4.8
>=2.5.0, <2.5.7
>=2.6.0, <2.6.5
2.3.1
2.4.8
2.5.7
2.6.5
bitnami ruby-min
<2.3.1
>=2.4.0, <2.4.8
>=2.5.0, <2.5.7
>=2.6.0, <2.6.5
2.3.1
2.4.8
2.5.7
2.6.5

Affected products

  • puma Puma

Classification

Weakness
  • CWE-113 Improper Neutralization of CRLF Sequences in HTTP Headers
  • CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.