ruby-secure-headers: CVE-2020-5216

Debian Bug report logs - #949998
ruby-secure-headers: CVE-2020-5216

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Salvatore Bonaccorso <carnil@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: ruby-secure-headers: CVE-2020-5216

Date: Tue, 28 Jan 2020 08:45:04 +0100

Source: ruby-secure-headers
Version: 6.1.1-1
Severity: important
Tags: security upstream

Hi,

The following vulnerability was published for ruby-secure-headers.

CVE-2020-5216[0]:
| 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.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-5216
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5216

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Send a report that this bug log contains spam.