Arbitrary Code Injection Affecting ruby-secure-headers package, versions <6.3.1-1


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.1% (43rd 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-DEBIANUNSTABLE-RUBYSECUREHEADERS-543268
  • published25 Jan 2020
  • disclosed23 Jan 2020

Introduced: 23 Jan 2020

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

How to fix?

Upgrade Debian:unstable ruby-secure-headers to version 6.3.1-1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream ruby-secure-headers package and not the ruby-secure-headers package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In Secure Headers (RubyGem secure_headers), a directive injection vulnerability is present in versions before 3.9.0, 5.2.0, and 6.3.0. If user-supplied input was passed into append/override_content_security_policy_directives, a newline could be injected leading to limited header injection. Upon seeing a newline in the header, rails will silently create a new Content-Security-Policy header with the remaining value of the original string. It will continue to create new headers for each newline. This has been fixed in 6.3.0, 5.2.0, and 3.9.0.

CVSS Base Scores

version 3.1