secure_headers up to 3.7.x/5.0.x/6.1.x override_content_security_policy_directives SecureHeaders::OPT_OUT eval injection

Summaryinfo

A vulnerability classified as critical was found in secure_headers up to 3.7.x/5.0.x/6.1.x. This issue affects the function SecureHeaders::OPT_OUT of the file append/override_content_security_policy_directives. Executing a manipulation can lead to eval injection. This vulnerability is handled as CVE-2020-5217. The attack can be executed remotely. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability has been found in secure_headers up to 3.7.x/5.0.x/6.1.x and classified as critical. This vulnerability affects the function SecureHeaders::OPT_OUT of the file append/override_content_security_policy_directives. The manipulation with an unknown input leads to a eval injection vulnerability. The CWE definition for the vulnerability is CWE-95. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. "eval"). As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

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.

The weakness was released 01/23/2020 (GitHub Repository). The advisory is shared for download at github.com. This vulnerability was named CVE-2020-5217 since 01/02/2020. The exploitation appears to be difficult. The attack can be initiated remotely. The successful exploitation requires a single authentication. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available.

Upgrading to version 3.8.0, 5.1.0 or 6.2.0 eliminates this vulnerability.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Name

• secure_headers

Version

• 3.0
• 3.1
• 3.2
• 3.3
• 3.4
• 3.5
• 3.6
• 3.7
• 5.0
• 6.0
• 6.1

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion