RHSA-2026:69098
Vulnerability from csaf_opensuse - Published: 2026-09-21 05:19 - Updated: 2026-09-30 23:37Out of bounds memory access in ANGLE in Google Chrome prior to 127.0.6533.99 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-0:2.54.0-1.el9_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-0:2.54.0-1.el9_8.i686 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-0:2.54.0-1.el9_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-0:2.54.0-1.el9_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-0:2.54.0-1.el9_8.src | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-0:2.54.0-1.el9_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-debuginfo-0:2.54.0-1.el9_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-debuginfo-0:2.54.0-1.el9_8.i686 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-debuginfo-0:2.54.0-1.el9_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-debuginfo-0:2.54.0-1.el9_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-debuginfo-0:2.54.0-1.el9_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-debugsource-0:2.54.0-1.el9_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-debugsource-0:2.54.0-1.el9_8.i686 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-debugsource-0:2.54.0-1.el9_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-debugsource-0:2.54.0-1.el9_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-debugsource-0:2.54.0-1.el9_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-devel-0:2.54.0-1.el9_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-devel-0:2.54.0-1.el9_8.i686 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-devel-0:2.54.0-1.el9_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-devel-0:2.54.0-1.el9_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-devel-0:2.54.0-1.el9_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-devel-debuginfo-0:2.54.0-1.el9_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-devel-debuginfo-0:2.54.0-1.el9_8.i686 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-devel-debuginfo-0:2.54.0-1.el9_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-devel-debuginfo-0:2.54.0-1.el9_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-devel-debuginfo-0:2.54.0-1.el9_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-jsc-0:2.54.0-1.el9_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-jsc-0:2.54.0-1.el9_8.i686 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-jsc-0:2.54.0-1.el9_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-jsc-0:2.54.0-1.el9_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-jsc-0:2.54.0-1.el9_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-jsc-debuginfo-0:2.54.0-1.el9_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-jsc-debuginfo-0:2.54.0-1.el9_8.i686 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-jsc-debuginfo-0:2.54.0-1.el9_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-jsc-debuginfo-0:2.54.0-1.el9_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-jsc-debuginfo-0:2.54.0-1.el9_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-jsc-devel-0:2.54.0-1.el9_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-jsc-devel-0:2.54.0-1.el9_8.i686 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-jsc-devel-0:2.54.0-1.el9_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-jsc-devel-0:2.54.0-1.el9_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-jsc-devel-0:2.54.0-1.el9_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-jsc-devel-debuginfo-0:2.54.0-1.el9_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-jsc-devel-debuginfo-0:2.54.0-1.el9_8.i686 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-jsc-devel-debuginfo-0:2.54.0-1.el9_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-jsc-devel-debuginfo-0:2.54.0-1.el9_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.8.0.Z.MAIN.EUS:webkit2gtk3-jsc-devel-debuginfo-0:2.54.0-1.el9_8.x86_64 | — |
Vendor Fix
fix
|
A flaw was found in chromium-browser. An out-of-bounds write vulnerability exists within the ANGLE graphics component, allowing a remote attacker to trigger out-of-bounds memory access by providing a specially crafted HTML page. This allows an attacker to potentially manipulate memory contents. The vulnerability is triggered by processing malicious graphics instructions. This can lead to unexpected program behavior.
Use after free in ANGLE in Google Chrome prior to 139.0.7258.154 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)
A Heap based buffer overflow issue has been ientified in ANGLE in Google Chrome that allowed a remote attacker to potentially exploit heap corruption via malicious network traffic.
Use after free in ANGLE in Google Chrome prior to 144.0.7559.59 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Low)
An integer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=485622239
A heap buffer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=486972661
An integer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=487977696
An integer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=487208468
A heap buffer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=489494022
An integer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=489791424
An inappropriate implementation flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=492131521
A heap buffer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=493256564
An insufficient validation of untrusted input flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=40073848
A heap buffer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=490170083
An integer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=497896137
An out of bounds read and write flaw was found in the Angle component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=498746519
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=496284494
A heap buffer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=496503799
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=497724490
An integer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=491760376
An integer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=495363705
An insufficient validation of untrusted input flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=495373657
An integer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=498400132
A heap buffer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=497928952
A type confusion flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=499131214
An inappropriate implementation flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500052361
An integer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=484986863
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=496445460
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=499054245
An out of bounds write flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=499129768
An integer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=506375217
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=497533569
An out of bounds write flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=497637277
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=497737770
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=498804020
An out of bounds read flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=499091328
An out of bounds memory access flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=499176133
An integer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=499205491
An inappropriate implementation flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500046096
An insufficient validation of untrusted input flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500047428
A heap buffer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500063836
An out of bounds write flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500080303
A heap buffer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500398345
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500536458
A heap buffer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500540748
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500540958
An out of bounds read flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=501125002
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=501563323
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=501584689
A heap buffer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=502738003
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=502812366
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=503438092
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=503471286
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=503596863
An out of bounds read flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=503985322
An out of bounds write flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=506377574
An insufficient validation of untrusted input flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=506550494
An out of bounds read and write flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=511719039
An insufficient validation of untrusted input flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513001247
An inappropriate implementation flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513364480
An integer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=504175501
An integer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=505056913
An out of bounds read and write flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=498904293
An out of bounds write flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=503768143
An out of bounds read flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513003797
An out of bounds write flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=489071023
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=497450927
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=497574371
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=498872764
A heap buffer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500429259
An out of bounds read flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500472605
A type confusion flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=506374676
An insufficient validation of untrusted input flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513135862
An out of bounds read flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513468021
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=504820809
An out of bounds memory access flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=489369089
An out of bounds read flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=494823889
An out of bounds read flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=495052581
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=498371085
An out of bounds write flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=498721316
An integer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=498724803
An out of bounds read flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=498828605
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=498881735
An out of bounds read flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=499031961
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=499093536
An insufficient validation of untrusted input flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=499124128
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500140149
An integer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500144879
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500161302
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500501226
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500524833
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500528864
An out of bounds read flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500530720
An insufficient validation of untrusted input flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500560764
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=501505198
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=501647943
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=501650354
An out of bounds memory access flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=503392431
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500528706
An insufficient validation of untrusted input flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=514769383
An out of bounds read flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=512962749
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513920082
An insufficient validation of untrusted input flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513925114
An inappropriate implementation flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=484756087
An insufficient validation of untrusted input flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=498820206
A type confusion flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500030250
An out of bounds read flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513857658
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=497670996
CWE-825 - Expired Pointer DereferenceAn uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513918431
An out of bounds write flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=517534944
An insufficient validation of untrusted input flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=250000 https://code.google.com/p/chromium/issues/detail?id=492218546
An out of bounds read flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=497543485
A heap buffer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=499006005
An out of bounds read flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=499047960
An out of bounds read flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500476886
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=503054174
An integer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=506212452
An out of bounds read flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=511737097
An out of bounds write flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=511772608
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=512995785
An out of bounds write flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513010645
An insufficient validation of untrusted input flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513048822
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513051340
An insufficient validation of untrusted input flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513919827
An insufficient validation of untrusted input flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513920834
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513922055
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=516865345
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=517935753
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=516899138
A flaw was found in ANGLE, a component of Chromium. A remote attacker who has compromised the renderer process could exploit an out-of-bounds write vulnerability by crafting a malicious HTML page. This could potentially allow the attacker to escape the sandbox, leading to further system compromise.
A flaw was found in Google Chrome's ANGLE component on Android. A remote attacker could exploit an out-of-bounds memory access vulnerability by enticing a user to visit a specially crafted HTML page. This could potentially allow the attacker to escape the browser's security sandbox, leading to further compromise of the system.
An insufficient validation of untrusted input flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=522556145
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513043537
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513134019
An insufficient validation of untrusted input flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513257423
An out of bounds write flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513920258
An inappropriate implementation flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513920298
An inappropriate implementation flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513921488
An out of bounds read flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=515452019
An integer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=516837126
An inappropriate implementation flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=516887576
A type confusion flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=516985726
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=517045160
An out of bounds write flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=517321292
An inappropriate implementation flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=517543052
A type confusion flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=517575864
An out of bounds read flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=517972648
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=519259107
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=521293438
An integer overflow flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=522063116
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=522079372
An out of bounds write flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=523495723
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=498827800
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=500560234
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513769898
An uninitialized use flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=513919931
An out of bounds memory access flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=514482938
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=516954622
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=517723319
An insufficient validation of untrusted input flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=518243653
An use after free flaw was found in the ANGLE component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=524639223
An use after free flaw was found in the Skia component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=532941869
A flaw was found in ANGLE, a component within Google Chrome on Android. This out-of-bounds write vulnerability allows a remote attacker to potentially perform a sandbox escape by enticing a user to visit a specially crafted HTML page. This could lead to an attacker executing arbitrary code outside the browser's security sandbox.
A flaw was found in Skia in Google Chrome. This uninitialized use vulnerability allows a remote attacker, who has already compromised the renderer process, to craft a malicious HTML page. Successful exploitation can lead to the leakage of sensitive cross-origin data.
An out of bounds write flaw was found in the Skia component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=538332338
A flaw was found in Skia, a 2D graphics library. A remote attacker, who has already compromised the renderer process, could exploit a use-after-free vulnerability by providing a specially crafted HTML page. This could lead to the execution of arbitrary code within the sandbox environment, potentially allowing further system compromise.
A flaw was found in WebKitGTK. Processing malicious web content can cause an unexpected process crash due to improper memory handling.
A flaw was found in WebKitGTK. Processing malicious web content can cause an unexpected process crash due to improper memory handling.
A flaw was found in WebKitGTK. Visiting a malicious website can cause an application denial of service due to improper state management.
A flaw was found in WebKitGTK. Visiting a website allows malicious web content to know if a user has visited a given link due to improper checks.
A flaw was found in WebKitGTK. Processing malicious web content can cause a use-after-free issue due to improper memory management and result in an unexpected process crash.
A flaw was found in WebKitGTK. Processing malicious web content can cause a use-after-free issue due to improper memory management and result in an unexpected process crash.
A flaw was found in WebKitGTK. Processing malicious web content can violate the iframe sandboxing policy due to improper validation.
A flaw was found in WebKitGTK. Visiting a website that frames malicious content can cause UI spoofing due to UI issues.
A flaw was found in WebKitGTK. Processing malicious web content can disclose sensitive user information due to a permission issue.
A flaw was found in WebKitGTK. Processing malicious web content can cause a memory corruption issue due to improper state management and result in an unexpected process crash.
A flaw was found in WebKitGTK. Visiting a malicious website may lead to a sensitive data leak due to improper validation checks.
A flaw was found in WebKitGTK. Processing malicious web content can cause an unexpected process crash due to improper locking.
A flaw was found in WebKitGTK. Processing malicious web content can cause an unexpected process crash due to improper validation checks.
A flaw was found in WebKitGTK. Processing malicious web content can cause an unexpected process crash due to improper locking.
A flaw was found in WebKitGTK. Processing malicious web content can cause a use-after-free issue due to improper memory management and result in an unexpected process crash.
A flaw was found in WebKitGTK. Processing malicious web content can cause an out-of-bounds access issue due to improper bounds checking and result in an unexpected process crash.
A flaw was found in WebKitGTK. Processing malicious web content can cause a use-after-free issue due to improper memory management and result in an unexpected process termination.
A flaw was found in WebKitGTK. Processing malicious web content can cause an unexpected process crash due to improper state management.
A flaw was found in WebKitGTK. Processing malicious web content can cause an unexpected process crash due to improper state management.
A flaw was found in WebKitGTK. Processing malicious web content can cause a memory corruption issue due to improper state management and result in an unexpected process crash.
A flaw was found in WebKitGTK. Processing malicious web content can cause an unexpected process crash due to improper state management.
A flaw was found in WebKitGTK. Processing malicious web content can cause an unexpected process crash due to improper state management.
A flaw was found in WebKitGTK. Processing malicious web content can cause an unexpected process crash due to improper state management.
A flaw was found in WebKitGTK. Processing malicious web content can cause an unexpected process crash due to improper memory handling.
A flaw was found in WebKitGTK. Processing malicious web content can cause an unexpected process crash due to improper state management.
A flaw was found in WebKitGTK. Processing malicious web content can cause memory corruption due to improper memory handling.
A flaw was found in WebKitGTK. Processing malicious web content can cause an unexpected process crash due to improper state management.
An information leak flaw was found in the Skia component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=540027341
A flaw was found in ANGLE, a component used in Google Chrome on Android. A remote attacker, who has already compromised the renderer process, could exploit a buffer overflow vulnerability by tricking a user into visiting a specially crafted HTML page. This could allow the attacker to execute arbitrary code outside of the browser's security sandbox, leading to a compromise of the affected system.
A flaw was found in WebKitGTK. Processing malicious web content can cause a use-after-free issue due to improper memory handling and result in memory corruption.
A flaw was found in ANGLE. A type confusion vulnerability in ANGLE, a graphics abstraction layer used in Google Chrome, allows a remote attacker to exploit the flaw. By crafting a malicious HTML page, the attacker can trigger this vulnerability. This could potentially lead to the execution of arbitrary code outside of the browser's security sandbox, compromising the affected system.
A flaw was found in ANGLE, a component used in Google Chrome. This type confusion vulnerability allows a remote attacker to potentially execute arbitrary code outside of the browser's security sandbox. Exploitation can occur by enticing a user to visit a specially crafted HTML page, leading to a compromise of the affected system.
A flaw was found in Chromium's ANGLE component. A race condition, triggered by a specially crafted HTML page, could allow a remote attacker to execute arbitrary code outside of the browser's security sandbox. This could lead to a complete compromise of the affected system.
A flaw was found in ANGLE, a component used in Google Chrome. A remote attacker could exploit an uninitialized resource vulnerability by tricking a user into visiting a specially crafted HTML page. This could allow the attacker to obtain sensitive cross-origin data, leading to information disclosure.
A flaw was found in ANGLE, a component within Google Chrome. A remote attacker could exploit an out-of-bounds read vulnerability by enticing a user to visit a specially crafted HTML page. This could potentially lead to the execution of arbitrary code outside of the browser's security sandbox.
A flaw was found in ANGLE, a component of Google Chrome on Windows. A remote attacker could exploit an out-of-bounds read vulnerability by enticing a user to visit a specially crafted HTML page. This could potentially allow the attacker to execute arbitrary code outside of the browser's security sandbox.
A flaw was found in ANGLE, a graphics abstraction layer used in Chromium-based browsers. A remote attacker could exploit an out-of-bounds write vulnerability by tricking a user into visiting a specially crafted HTML page. This could potentially allow the attacker to execute arbitrary code outside of the browser's security sandbox.
An out of bounds read flaw was found in the Skia component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=514017820
A flaw was found in ANGLE, a component used in Google Chrome. A remote attacker could exploit an out-of-bounds write vulnerability by tricking a user into visiting a specially crafted HTML page. This could potentially allow the attacker to execute arbitrary code outside of the browser's security sandbox, leading to a compromise of the affected system.
A flaw was found in ANGLE, a graphics abstraction layer used in Google Chrome. A remote attacker could exploit an out-of-bounds write vulnerability by enticing a user to visit a specially crafted HTML page. This could potentially allow the attacker to execute arbitrary code within the sandbox environment.
A flaw was found in Chromium's ANGLE component. A remote attacker could exploit an uninitialized resource vulnerability by enticing a user to visit a specially crafted HTML page. This could lead to the disclosure of sensitive cross-origin data.
A flaw was found in ANGLE in Google Chrome. An uninitialized resource vulnerability exists that allows a remote attacker to potentially obtain cross-origin data by enticing a user to visit a crafted HTML page.
A flaw was found in ANGLE in Google Chrome. A remote attacker could exploit an out-of-bounds write vulnerability by enticing a user to visit a specially crafted HTML page. This could allow the attacker to execute arbitrary code outside of the browser's security sandbox, leading to a compromise of the affected system.
A flaw was found in ANGLE, a component used by Google Chrome. A remote attacker could exploit this buffer overflow vulnerability by tricking a user into visiting a specially crafted HTML page. This could lead to the execution of arbitrary code outside of the browser's security sandbox, potentially compromising the affected system.
A flaw was found in ANGLE, a component of Chromium. A remote attacker could exploit an out-of-bounds write vulnerability by enticing a user to visit a specially crafted HTML page. This could lead to arbitrary code execution outside of the sandbox, allowing the attacker to gain control over the affected system.
A flaw was found in chromium-browser. An out-of-bounds write vulnerability in ANGLE, a component used for graphics rendering, could allow a remote attacker to execute malicious code. This vulnerability can be exploited by tricking a user into visiting a specially crafted web page. Successful exploitation could lead to arbitrary code execution, potentially allowing the attacker to take control of the affected system.
A flaw was found in ANGLE, a component used in Google Chrome on Android. This buffer overflow vulnerability allows a remote attacker to execute arbitrary code outside of the browser's security sandbox. The exploitation occurs when a user visits a specially crafted HTML page, leading to a severe compromise of the affected system.
A flaw was found in ANGLE, a component used in Google Chrome. This use-after-free vulnerability allows a remote attacker to execute arbitrary code outside of the sandbox by tricking a user into visiting a specially crafted HTML page. This could lead to a complete compromise of the affected system.
A flaw was found in the ANGLE component of Google Chrome. A remote attacker could exploit an out-of-bounds write vulnerability by enticing a user to visit a specially crafted HTML page. This could potentially allow the attacker to execute arbitrary code outside of the browser's security sandbox.
A flaw was found in ANGLE, a component used in chromium-browser. A remote attacker could exploit an out-of-bounds write vulnerability by enticing a user to visit a specially crafted HTML page. This could potentially lead to the execution of arbitrary code outside of the browser's security sandbox, allowing the attacker to gain control over the affected system.
A flaw was found in ANGLE, a component within Chromium. This uninitialized resource vulnerability could allow a remote attacker, who has already compromised the renderer process, to read sensitive memory outside of the security sandbox. This exploitation can occur by tricking a user into visiting a specially crafted HTML page, leading to unauthorized information disclosure.
A flaw was found in ANGLE, a component of Google Chrome. Improper input validation could allow a remote attacker to execute arbitrary code outside of the browser's security sandbox by enticing a user to visit a specially crafted HTML page. This could lead to a complete compromise of the affected system.
A flaw was found in ANGLE in Google Chrome. A remote attacker could exploit an out-of-bounds write vulnerability by enticing a user to visit a specially crafted HTML page. This could potentially lead to arbitrary code execution within the sandbox environment.
A flaw was found in ANGLE, a component of Chromium. A remote attacker could exploit an uninitialized resource vulnerability by enticing a user to visit a specially crafted HTML page. This could potentially allow the attacker to bypass the web origin policy, leading to unauthorized access to sensitive information or actions.
A flaw was found in chromium-browser. A remote attacker could exploit an uninitialized resource vulnerability in ANGLE by crafting a malicious HTML page. This could allow the attacker to read sensitive memory outside of the browser's security sandbox.
A flaw was found in ANGLE, a component of Google Chrome. This use-after-free vulnerability allows a remote attacker to execute arbitrary code outside the browser's security sandbox. The attacker could exploit this by enticing a user to visit a specially crafted HTML page.
A flaw was found in ANGLE, a component of Google Chrome on Android. This 'use after free' vulnerability allows a remote attacker to execute arbitrary code outside the browser's security sandbox. This can be exploited by enticing a user to visit a specially crafted HTML page. Successful exploitation could lead to a complete compromise of the affected device.
A flaw was found in ANGLE, a component used by Google Chrome. A remote attacker could exploit an uninitialized resource vulnerability by enticing a user to visit a specially crafted HTML page. This could allow the attacker to obtain sensitive cross-origin data, leading to information disclosure.
A flaw was found in WebKitGTK. Processing malicious web content can cause memory corruption due to improper memory handling.
A flaw was found in WebKitGTK. Processing malicious web content can cause an unexpected process termination due to improper state management.
Loading 3.7 MB of JSON…
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.