CVE-2016-1633
published 2016-03-06CVE-2016-1633: Use-after-free vulnerability in Blink, as used in Google Chrome before 49.0.2623.75, allows remote attackers to cause a denial of service or possibly have…
PriorityP340critical9.8CVSS 3.0
AVNACLPRNUINSUCHIHAH
EPSS
2.45%
82.8th percentile
Use-after-free vulnerability in Blink, as used in Google Chrome before 49.0.2623.75, allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| chrome | <= 48.0.2564.116 | — |
CVSS provenance
nvdv3.09.8CRITICALCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvdv2.010.0CRITICALAV:N/AC:L/Au:N/C:C/I:C/A:C
osv9.8CRITICAL
vendor_redhat9.8CRITICAL
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-02·CVSS 9.8
CVE-2016-1633 [CRITICAL] CWE-416 chromium-browser: use-after-free in Blink
chromium-browser: use-after-free in Blink
Use-after-free vulnerability in Blink, as used in Google Chrome before 49.0.2623.75, allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors.
GHSA
GHSA-8c97-jjmh-4pxp: Use-after-free vulnerability in Blink, as used in Google Chrome before 49
ghsa_unreviewed·2022-05-17
CVE-2016-1633 [CRITICAL] GHSA-8c97-jjmh-4pxp: Use-after-free vulnerability in Blink, as used in Google Chrome before 49
Use-after-free vulnerability in Blink, as used in Google Chrome before 49.0.2623.75, allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors.
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-1633: Use-after-free vulnerability in Blink, as used in Google Chrome before 49
osv·2016-03-05·CVSS 9.8
CVE-2016-1633 [CRITICAL] CVE-2016-1633: Use-after-free vulnerability in Blink, as used in Google Chrome before 49
Use-after-free vulnerability in Blink, as used in Google Chrome before 49.0.2623.75, allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2016-3658 libtiff: out-of-bounds read in the TIFFWriteDirectoryTagLongLong8Array function
bugzilla·2016-04-12·CVSS 6.5
CVE-2016-3658 [MEDIUM] CVE-2016-3658 libtiff: out-of-bounds read in the TIFFWriteDirectoryTagLongLong8Array function
CVE-2016-3658 libtiff: out-of-bounds read in the TIFFWriteDirectoryTagLongLong8Array function
A vulnerability was found in the libtiff library. Using a tiffset command on a maliciously crafted image could result in a denial-of-service.
Vulnerable code:
/libtiff/tif_dirwrite.c: 1625
1623 for (q=p, ma=value, mb=0; mb0xFFFFFFFF)
1626 {
1627 TIFFErrorExt(tif->tif_clientdata,module,
1628 "Attempt to write value larger than 0xFFFFFFFF in Classic TIFF file.");
1629 _TIFFfree(p);
1630 return(0);
1631 }
1632 *q= (uint32)(*ma);
1633 }
References:
http://www.openwall.com/lists/oss-security/2016/04/08/12
Discussion:
External References:
http://bugzilla.maptools.org/show_bug.cgi?id=2546
---
*** This bug has been marked as a duplicate of bug 1185805 ***
---
Statement:
This flaw was found to
Bugzilla
CVE-2016-1633 chromium-browser: use-after-free in Blink
bugzilla·2016-03-03·CVSS 9.8
CVE-2016-1633 [CRITICAL] CVE-2016-1633 chromium-browser: use-after-free in Blink
CVE-2016-1633 chromium-browser: use-after-free in Blink
A use-after-free flaw was found in the Blink component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=572537
External References:
http://googlechromereleases.blogspot.com/2016/03/stable-channel-update.html
Discussion:
This issue has been addressed in the following products:
Supplementary for Red Hat Enterprise Linux 6
Via RHSA-2016:0359 https://rhn.redhat.com/errata/RHSA-2016-0359.html
http://googlechromereleases.blogspot.com/2016/03/stable-channel-update.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-03/msg00014.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-03/msg00015.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-03/msg00018.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-03/msg00028.htmlhttp://www.debian.org/security/2016/dsa-3507http://www.securityfocus.com/bid/84008http://www.securitytracker.com/id/1035185http://www.ubuntu.com/usn/USN-2920-1https://code.google.com/p/chromium/issues/detail?id=572537https://security.gentoo.org/glsa/201603-09http://googlechromereleases.blogspot.com/2016/03/stable-channel-update.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-03/msg00014.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-03/msg00015.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-03/msg00018.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-03/msg00028.htmlhttp://www.debian.org/security/2016/dsa-3507http://www.securityfocus.com/bid/84008http://www.securitytracker.com/id/1035185http://www.ubuntu.com/usn/USN-2920-1https://code.google.com/p/chromium/issues/detail?id=572537https://security.gentoo.org/glsa/201603-09
2016-03-06
Published