CVE-2020-5217

Medium

Description

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.

SeverityMedium
CVSS4.4
Exploit probability—
ProductTwitter Secure Headers
PublishedJan 23, 2020
First seenJan 23, 2020
Weakness typeCWE-95CWE-95

How to fix

Update
  • twitter secure_headers3.8.0, 5.1.0, 6.2.0 or later

Affected products

ProductAffected versionsFixed in
twitter secure_headersv < 3.8.0, 5.0.0 ≤ v < 5.1.0, 6.0.0 ≤ v < 6.2.03.8.0, 5.1.0, 6.2.0

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.

CVE-2020-5217 · Twitter Secure Headers · Dark Radar