CVE-2016-1644
published 2016-03-13CVE-2016-1644: WebKit/Source/core/layout/LayoutObject.cpp in Blink, as used in Google Chrome before 49.0.2623.87, does not properly restrict relayout scheduling, which allows…
PriorityP337high8.8CVSS 3.0
AVNACLPRNUIRSUCHIHAH
EPSS
2.06%
79.5th percentile
WebKit/Source/core/layout/LayoutObject.cpp in Blink, as used in Google Chrome before 49.0.2623.87, does not properly restrict relayout scheduling, which allows remote attackers to cause a denial of service (use-after-free) or possibly have unspecified other impact via a crafted HTML document.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| chrome | <= 49.0.2623.75 | — |
CVSS provenance
nvdv3.08.8HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvdv2.09.3CRITICALAV:N/AC:M/Au:N/C:C/I:C/A:C
osv8.8HIGH
vendor_redhat8.8HIGH
vendor_ubuntu8.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Ubuntu
Oxide vulnerabilities
vendor_ubuntu·2016-03-10·CVSS 8.8
CVE-2016-1630 [HIGH] Oxide vulnerabilities
Title: Oxide vulnerabilities
Summary: Several security issues were fixed in Oxide.
It was discovered that the ContainerNode::parserRemoveChild function in
Blink mishandled widget updates in some circumstances. If a user were
tricked in to opening a specially crafted website, an attacker could
potentially exploit this to bypass same-origin restrictions.
(CVE-2016-1630)
It was discovered that the PPB_Flash_MessageLoop_Impl::InternalRun
function in Chromium mishandled nested message loops. If a user were
tricked in to opening a specially crafted website, an attacker could
potentially exploit this to bypass same-origin restrictions.
(CVE-2016-1631)
Multiple use-after-frees were discovered in Blink. If a user were tricked
in to opening a specially crafted website, an attacker could potentia
Red Hat
chromium-browser: use-after-free in Blink
vendor_redhat·2016-03-08·CVSS 8.8
CVE-2016-1644 [HIGH] CWE-416 chromium-browser: use-after-free in Blink
chromium-browser: use-after-free in Blink
WebKit/Source/core/layout/LayoutObject.cpp in Blink, as used in Google Chrome before 49.0.2623.87, does not properly restrict relayout scheduling, which allows remote attackers to cause a denial of service (use-after-free) or possibly have unspecified other impact via a crafted HTML document.
GHSA
GHSA-xg2h-74jh-cx48: WebKit/Source/core/layout/LayoutObject
ghsa_unreviewed·2022-05-17
CVE-2016-1644 [HIGH] GHSA-xg2h-74jh-cx48: WebKit/Source/core/layout/LayoutObject
WebKit/Source/core/layout/LayoutObject.cpp in Blink, as used in Google Chrome before 49.0.2623.87, does not properly restrict relayout scheduling, which allows remote attackers to cause a denial of service (use-after-free) or possibly have unspecified other impact via a crafted HTML document.
OSV
oxide-qt vulnerabilities
osv·2016-03-10·CVSS 8.8
CVE-2016-1630 [HIGH] oxide-qt vulnerabilities
oxide-qt vulnerabilities
It was discovered that the ContainerNode::parserRemoveChild function in
Blink mishandled widget updates in some circumstances. If a user were
tricked in to opening a specially crafted website, an attacker could
potentially exploit this to bypass same-origin restrictions.
(CVE-2016-1630)
It was discovered that the PPB_Flash_MessageLoop_Impl::InternalRun
function in Chromium mishandled nested message loops. If a user were
tricked in to opening a specially crafted website, an attacker could
potentially exploit this to bypass same-origin restrictions.
(CVE-2016-1631)
Multiple use-after-frees were discovered in Blink. If a user were tricked
in to opening a specially crafted website, an attacker could potentially
exploit these to cause a denial of service via renderer
OSV
CVE-2016-1644: WebKit/Source/core/layout/LayoutObject
osv·2016-03-10·CVSS 8.8
CVE-2016-1644 [HIGH] CVE-2016-1644: WebKit/Source/core/layout/LayoutObject
WebKit/Source/core/layout/LayoutObject.cpp in Blink, as used in Google Chrome before 49.0.2623.87, does not properly restrict relayout scheduling, which allows remote attackers to cause a denial of service (use-after-free) or possibly have unspecified other impact via a crafted HTML document.
No detection rules found.
No public exploits indexed.
http://googlechromereleases.blogspot.com/2016/03/stable-channel-update_8.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-03/msg00066.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-03/msg00067.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-03/msg00073.htmlhttp://www.debian.org/security/2016/dsa-3513http://www.securityfocus.com/bid/84224http://www.securitytracker.com/id/1035259http://www.ubuntu.com/usn/USN-2920-1https://code.google.com/p/chromium/issues/detail?id=590620https://codereview.chromium.org/1755543002http://googlechromereleases.blogspot.com/2016/03/stable-channel-update_8.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-03/msg00066.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-03/msg00067.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-03/msg00073.htmlhttp://www.debian.org/security/2016/dsa-3513http://www.securityfocus.com/bid/84224http://www.securitytracker.com/id/1035259http://www.ubuntu.com/usn/USN-2920-1https://code.google.com/p/chromium/issues/detail?id=590620https://codereview.chromium.org/1755543002
2016-03-13
Published