GHSA-xq52-rv6w-397c

Suggest an improvement
Source
https://github.com/advisories/GHSA-xq52-rv6w-397c
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2020/01/GHSA-xq52-rv6w-397c/GHSA-xq52-rv6w-397c.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-xq52-rv6w-397c
Aliases
Published
2020-01-23T02:28:11Z
Modified
2023-11-08T04:03:51.493508Z
Severity
  • 4.4 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N CVSS Calculator
Summary
Directive injection when using dynamic overrides with user input
Details

Impact

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.

Duplicate script-src directives detected. All but the first instance will be ignored.

See https://www.w3.org/TR/CSP3/#parse-serialized-policy

Note: In this case, the user agent SHOULD notify developers that a duplicate directive was ignored. A console warning might be appropriate, for example.

Patches

Depending on what major version you are using, the fixed versions are 6.2.0, 5.1.0, 3.8.0.

Workarounds

If you are passing user input into the above methods, you could filter out the input:

override_content_security_policy_directives(:frame_src, [user_input.gsub(";", " ")])

References

Reported in https://github.com/twitter/secure_headers/issues/418 https://www.w3.org/TR/CSP3/#parse-serialized-policy

For more information

If you have any questions or comments about this advisory: * Open an issue in this repo * DM @ndm on twitter

Database specific 
{
    "nvd_published_at": null,
    "cwe_ids": [
        "CWE-95"
    ],
    "severity": "MODERATE",
    "github_reviewed": true,
    "github_reviewed_at": "2020-01-23T02:12:03Z"
}
References

Affected packages

RubyGems / secure_headers

Package

Name
secure_headers
Purl
pkg:gem/secure_headers

Affected ranges

Type
ECOSYSTEM
Events
Introduced
6.0.0
Fixed
6.2.0

Affected versions

6.*

6.0.0
6.1.0
6.1.1
6.1.2

RubyGems / secure_headers

Package

Name
secure_headers
Purl
pkg:gem/secure_headers

Affected ranges

Type
ECOSYSTEM
Events
Introduced
5.0.0
Fixed
5.1.0

Affected versions

5.*

5.0.1
5.0.2
5.0.3
5.0.4
5.0.5

RubyGems / secure_headers

Package

Name
secure_headers
Purl
pkg:gem/secure_headers

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
3.8.0

Affected versions

0.*

0.1.0
0.1.1
0.2.0
0.2.1
0.3.0
0.4.0
0.4.1
0.4.2
0.4.3
0.5.0

1.*

1.0.0
1.1.0
1.1.1
1.2.0
1.3.0
1.3.1
1.3.2
1.3.3
1.3.4
1.4.0
1.4.1

2.*

2.0.0.pre
2.0.0.pre2
2.0.0
2.0.1
2.0.2
2.1.0
2.2.0
2.2.1
2.2.2
2.2.3
2.2.4
2.3.0
2.4.0
2.4.1
2.4.2
2.4.3
2.4.4
2.5.0
2.5.1
2.5.2
2.5.3

3.*

3.0.0.pre
3.0.0.pre1
3.0.0.pre2
3.0.0.pre3
3.0.0.rc1
3.0.0
3.0.1
3.0.2
3.0.3
3.1.0
3.1.1
3.1.2
3.2.0
3.3.0
3.3.1
3.3.2
3.4.0
3.4.1
3.5.0.pre
3.5.0
3.5.1
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
3.7.0
3.7.1
3.7.2
3.7.3
3.7.4