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.2% (59th 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-543273
  • published25 Jan 2020
  • disclosed23 Jan 2020

Introduced: 23 Jan 2020

CVE-2020-5217  (opens in a new tab)
CWE-74  (opens in a new tab)
CWE-95  (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.8.0, 5.1.0, and 6.2.0. If user-supplied input was passed into append/override_content_security_policy_directives, a semicolon could be injected leading to directive injection. This could be used to e.g. override a script-src directive. Duplicate directives are ignored and the first one wins. The directives in secure_headers are sorted alphabetically so they pretty much all come before script-src. A previously undefined directive would receive a value even if SecureHeaders::OPT_OUT was supplied. The fixed versions will silently convert the semicolons to spaces and emit a deprecation warning when this happens. This will result in innocuous browser console messages if being exploited/accidentally used. In future releases, we will raise application errors resulting in 500s. Depending on what major version you are using, the fixed versions are 6.2.0, 5.1.0, 3.8.0.

CVSS Base Scores

version 3.1