HTTP Response Splitting Affecting rmt-server-config package, versions <2.6.5-3.3.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
1.03% (84th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES152-RMTSERVERCONFIG-2698306
  • published14 Apr 2022
  • disclosed26 Oct 2020

Introduced: 26 Oct 2020

CVE-2020-5247  (opens in a new tab)
CWE-113  (opens in a new tab)

How to fix?

Upgrade SLES:15.2 rmt-server-config to version 2.6.5-3.3.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rmt-server-config package and not the rmt-server-config package as distributed by SLES. See How to fix? for SLES:15.2 relevant fixed versions and status.

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.

CVSS Scores

version 3.1