CVE-2020-5217
Twitter Secure Headers vulnerability
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.
Affected products
Secure Headers. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Twitter Secure Headers runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/twitter/secure_headers/commit/936a160e3e9659737a9f9eafce13eea36b5c9fa3 · Patch
- github.com/twitter/secure_headers/security/advisories/GHSA-xq52-rv6w-397c · Mitigation
- github.com/twitter/secure_headers/issues/418 · Exploit
- github.com/twitter/secure_headers/pull/421 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2020-5217
- cve.org/CVERecord?id=CVE-2020-5217
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.