CVE-2023-1226: Insufficient policy enforcement in Web Payments API
Published Oct 10, 2019
·Updated
Insufficient policy enforcement in Web Payments API in Google Chrome prior to 111.0.5563.64 allowed a remote attacker to bypass content security policy via a crafted HTML page. (Chromium security severity: Medium)
Credit
Anonymous
Affected Software
2 affected componentsFixes available
Google Chrome<111.0.5563.64
111.0.5563.64
Google Chrome<111.0.5563.64
Event History
Oct 10, 2019
CVE Published
12:00 AM
Mar 7, 2023
CVE Published
via MITRE·09:42 PM
Data Sourced
via MITRE·09:42 PM
DescriptionWeakness
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2023-1213
- CVE-2023-1214
- CVE-2023-1215
- CVE-2023-1216
- CVE-2023-1217
- CVE-2023-1218
- CVE-2023-1219
- CVE-2023-1220
- CVE-2023-1221
- CVE-2023-1222
- CVE-2023-1223
- CVE-2023-1224
- CVE-2023-1225
- CVE-2023-1227
- CVE-2023-1228
- CVE-2023-1229
- CVE-2023-1230
- CVE-2023-1231
- CVE-2023-2314
- CVE-2023-1232
- CVE-2023-1233
- CVE-2023-1234
- CVE-2023-1235
- CVE-2023-1236
Frequently Asked Questions
1
What is the severity of CVE-2023-1226?
CVE-2023-1226 has a medium severity rating as per Chromium security assessment.
2
How do I fix CVE-2023-1226?
To fix CVE-2023-1226, update Google Chrome to version 111.0.5563.64 or later.
3
What causes CVE-2023-1226?
CVE-2023-1226 is caused by insufficient policy enforcement in the Web Payments API.
4
Which versions of Google Chrome are affected by CVE-2023-1226?
Google Chrome versions prior to 111.0.5563.64 are affected by CVE-2023-1226.
5
Can CVE-2023-1226 be exploited remotely?
Yes, CVE-2023-1226 allows remote attackers to bypass content security policy through a crafted HTML page.