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.
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
| Link | Tags |
|---|---|
| https://crbug.com/808192 | exploit issue tracking |
| https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html | vendor advisory release notes |
| http://www.securityfocus.com/bid/103297 | third party advisory broken link vdb entry |
| https://access.redhat.com/errata/RHSA-2018:0484 | vendor advisory third party advisory |
| https://www.exploit-db.com/exploits/44584/ | third party advisory exploit vdb entry |
| https://www.debian.org/security/2018/dsa-4182 | third party advisory vendor advisory mailing list |
| https://www.zerodayinitiative.com/advisories/ZDI-19-367/ | vdb entry third party advisory |