CVE-2020-5216
Published: 23 January 2020
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.
Priority
Status
Package | Release | Status |
---|---|---|
ruby-secure-headers Launchpad, Ubuntu, Debian |
bionic |
Needed
|
eoan |
Ignored
(end of life)
|
|
focal |
Needed
|
|
groovy |
Not vulnerable
(6.3.1-1)
|
|
hirsute |
Not vulnerable
(6.3.1-1)
|
|
impish |
Not vulnerable
(6.3.1-1)
|
|
jammy |
Not vulnerable
(6.3.1-1)
|
|
kinetic |
Not vulnerable
(6.3.1-1)
|
|
lunar |
Not vulnerable
(6.3.1-1)
|
|
mantic |
Not vulnerable
(6.3.1-1)
|
|
noble |
Not vulnerable
(6.3.1-1)
|
|
trusty |
Does not exist
|
|
upstream |
Needed
|
|
xenial |
Does not exist
|
Severity score breakdown
Parameter | Value |
---|---|
Base score | 5.8 |
Attack vector | Network |
Attack complexity | Low |
Privileges required | None |
User interaction | None |
Scope | Changed |
Confidentiality | None |
Integrity impact | Low |
Availability impact | None |
Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N |