Vulnerability in secure_headers (CVE-2020-5216)
Summary
Vulnerability in secure_headers (CVE-2020-5216). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 6.3.0 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-5216 has been found in secure_headers.
Risk of unauthorized operations or information disclosure.
What to do: upgrade secure_headers to 6.3.0 or later.
If unsure, ask your IT team or search "secure_headers CVE-2020-5216" on the vendor's site.
CVE-2020-5216 (secure_headers) — CWE-113
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 6.3.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-113) exists in secure_headers.
Check the vendor advisory for the affected versions of secure_headers.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 6.3.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'secure_headers' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'secure_headers' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
secure_headersを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade secure_headers to 6.3.0ステージング環境で 6.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2020-5216 ruby-secure-headers Fixed in: 6.3.1-1
References
- advisory nvd.nist.gov
- package github.com
- patch github.com
- report github.com
- web github.com