Описание
Integer overflow in computing the required allocation size when instantiating a new javascript object in V8 in Google Chrome prior to 65.0.3325.146 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Integer overflow in computing the required allocation size when instantiating a new javascript object in V8 in Google Chrome prior to 65.0.3325.146 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2018-6065
- https://access.redhat.com/errata/RHSA-2018:0484
- https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html
- https://crbug.com/808192
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2018-6065
- https://www.debian.org/security/2018/dsa-4182
- https://www.exploit-db.com/exploits/44584
- https://www.zerodayinitiative.com/advisories/ZDI-19-367
- http://www.securityfocus.com/bid/103297
Связанные уязвимости
Integer overflow in computing the required allocation size when instantiating a new javascript object in V8 in Google Chrome prior to 65.0.3325.146 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Integer overflow in computing the required allocation size when instantiating a new javascript object in V8 in Google Chrome prior to 65.0.3325.146 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Integer overflow in computing the required allocation size when instantiating a new javascript object in V8 in Google Chrome prior to 65.0.3325.146 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Integer overflow in computing the required allocation size when instan ...
Уязвимость обработчика JavaScript-сценариев V8 браузера Google Chrome, позволяющая нарушителю выполнить произвольный код