CVE-2020-5216: Limited header injection when using dynamic overrides with user input in RubyGems secure_headers
Twitter · secure_headers
Affected: Twitter secure_headers · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 68% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Twitter · secure_headers< 3.9.0; >= 5.0.0, < 5.2.0; >= 6.0.0, < 6.3.0
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Published
- January 2020
CoverageNo articles yet
No CyberSIXT article names CVE-2020-5216 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.