Bug 1879540 (CVE-2020-9915) - CVE-2020-9915 webkitgtk: Access issue in content security policy
Summary: CVE-2020-9915 webkitgtk: Access issue in content security policy
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2020-9915
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1881729 1881730 1881731
Blocks: 1879543
TreeView+ depends on / blocked
 
Reported: 2020-09-16 13:48 UTC by Pedro Sampaio
Modified: 2025-07-07 02:24 UTC (History)
3 users (show)

Fixed In Version: webkitgtk 2.28.4
Clone Of:
Environment:
Last Closed: 2020-11-04 02:26:52 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:4451 0 None None None 2020-11-04 01:05:31 UTC
Red Hat Product Errata RHSA-2025:10364 0 None None None 2025-07-07 02:24:25 UTC

Description Pedro Sampaio 2020-09-16 13:48:41 UTC 
An access issue existed in Content Security Policy. Processing maliciously crafted web content may prevent Content Security Policy from being enforced. Versions affected: WebKitGTK before 2.28.4 and WPE WebKit before 2.28.4.
Comment 1 Pedro Sampaio 2020-09-16 13:48:45 UTC 
External References:

https://webkitgtk.org/security/WSA-2020-0007.html
Comment 3 errata-xmlrpc 2020-11-04 01:05:29 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2020:4451 https://access.redhat.com/errata/RHSA-2020:4451
Comment 4 Product Security DevOps Team 2020-11-04 02:26:52 UTC 
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2020-9915
Comment 5 errata-xmlrpc 2025-07-07 02:24:23 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7 Extended Lifecycle Support

Via RHSA-2025:10364 https://access.redhat.com/errata/RHSA-2025:10364
Note You need to log in before you can comment on or make changes to this bug.