CVE-2016-5129
published 2016-07-23CVE-2016-5129: Google V8 before 5.2.361.32, as used in Google Chrome before 52.0.2743.82, does not properly process left-trimmed objects, which allows remote attackers to…
PriorityP434high8.8CVSS 3.0
AVNACLPRNUIRSUCHIHAH
EPSS
2.09%
79.6th percentile
Google V8 before 5.2.361.32, as used in Google Chrome before 52.0.2743.82, does not properly process left-trimmed objects, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via crafted JavaScript code.
Affected
4 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| android | — | — | |
| chrome | — | — | |
| v8 | <= 5.2.360 | — | |
| nodejs | nodejs | >= 0 < 6.10.0-r0 | 6.10.0-r0 |
CVSS provenance
nvdv3.08.8HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvdv2.06.8MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:P
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.
Android
CVE-2016-5129: Android Security Bulletin 2017-04-01
CVE: CVE-2016-5129
Severity: HIGH
Affected AOSP versions: 6
vendor_android·2017-04-01·CVSS 8.8
CVE-2016-5129 [HIGH] CVE-2016-5129: Android Security Bulletin 2017-04-01
CVE: CVE-2016-5129
Severity: HIGH
Affected AOSP versions: 6
Android Security Bulletin 2017-04-01
CVE: CVE-2016-5129
Severity: HIGH
Affected AOSP versions: 6.0, 6.0.1, 7.0
References: A-29178923
Ubuntu
Oxide vulnerabilities
vendor_ubuntu·2016-08-05·CVSS 8.8
CVE-2016-1705 [HIGH] Oxide vulnerabilities
Title: Oxide vulnerabilities
Summary: Several security issues were fixed in Oxide.
Multiple security issues were discovered in Chromium. If a user were
tricked in to opening a specially crafted website, an attacker could
potentially exploit these to read uninitialized memory, cause a denial
of service (application crash) or execute arbitrary code. (CVE-2016-1705)
It was discovered that the PPAPI implementation does not validate the
origin of IPC messages to the plugin broker process. A remote attacker
could potentially exploit this to bypass sandbox protection mechanisms.
(CVE-2016-1706)
It was discovered that Blink does not prevent window creation by a
deferred frame. A remote attacker could potentially exploit this to bypass
same origin restrictions. (CVE-2016-1710)
It was discovere
Red Hat
chromium-browser: memory corruption in v8
vendor_redhat·2016-07-20·CVSS 8.8
CVE-2016-5129 [HIGH] chromium-browser: memory corruption in v8
chromium-browser: memory corruption in v8
Google V8 before 5.2.361.32, as used in Google Chrome before 52.0.2743.82, does not properly process left-trimmed objects, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via crafted JavaScript code.
GHSA
GHSA-2c2c-vqcm-ccr6: Google V8 before 5
ghsa_unreviewed·2022-05-17
CVE-2016-5129 [HIGH] CWE-119 GHSA-2c2c-vqcm-ccr6: Google V8 before 5
Google V8 before 5.2.361.32, as used in Google Chrome before 52.0.2743.82, does not properly process left-trimmed objects, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via crafted JavaScript code.
OSV
oxide-qt vulnerabilities
osv·2016-08-05·CVSS 8.8
CVE-2016-1705 [HIGH] oxide-qt vulnerabilities
oxide-qt vulnerabilities
Multiple security issues were discovered in Chromium. If a user were
tricked in to opening a specially crafted website, an attacker could
potentially exploit these to read uninitialized memory, cause a denial
of service (application crash) or execute arbitrary code. (CVE-2016-1705)
It was discovered that the PPAPI implementation does not validate the
origin of IPC messages to the plugin broker process. A remote attacker
could potentially exploit this to bypass sandbox protection mechanisms.
(CVE-2016-1706)
It was discovered that Blink does not prevent window creation by a
deferred frame. A remote attacker could potentially exploit this to bypass
same origin restrictions. (CVE-2016-1710)
It was discovered that Blink does not disable frame navigation during a
det
OSV
CVE-2016-5129: Google V8 before 5
osv·2016-07-23·CVSS 8.8
CVE-2016-5129 [HIGH] CVE-2016-5129: Google V8 before 5
Google V8 before 5.2.361.32, as used in Google Chrome before 52.0.2743.82, does not properly process left-trimmed objects, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via crafted JavaScript code.
No detection rules found.
No public exploits indexed.
arXiv
SOK: On the Analysis of Web Browser Security
arxiv_fulltext·2021-12-31
SOK: On the Analysis of Web Browser Security
: On the Analysis of Web Browser Security
fancyplain
Rev.
\ of LastPage
Jungwon Lim*,\;
Yonghwi Jin*^ ,\;
Mansour Alharthi,\;
Xiaokuan Zhang,\;
Jinho Jung,\;
Rajat Gupta,\;
Kuilin Li,\;
Daehee Jang^ ,\;
Taesoo Kim\;
Georgia Institute of Technology ^ Theori Inc. ^ Sungshin Women's University
## Abstract
Web browsers are integral parts of everyone's daily life.
They are commonly used
for security-critical and privacy sensitive tasks,
like banking transactions and checking medical records.
Unfortunately,
modern web browsers are
too complex to be bug free
( , 25 million lines of code in Chrome),
and their role as an interface to the cyberspace
makes them an attractive target for attacks.
Accordingly,
web browsers naturally
become an arena for demonstrating
advanced exploitation techni
arXiv
Rethinking Misalignment to Raise the Bar for Heap Pointer Corruption
arxiv_fulltext·2018-08-08
Rethinking Misalignment to Raise the Bar for Heap Pointer Corruption
Rethinking Misalignment to Raise the Bar for Heap Pointer Corruption
Daehee Jang
KAIST
[email protected]
Hojoon Lee
KAIST
[email protected]
Brent Byunghoon Kang
KAIST
[email protected]
Michael Shell
Georgia Institute of Technology
[email protected]
Homer Simpson
Twentieth Century Fox
[email protected]
James Kirk
and Montgomery Scott
Starfleet Academy
[email protected]
\@IEEEpubidpullup9
Permission to freely reproduce all or part
of this paper for noncommercial purposes is granted provided that
copies bear this notice and the full citation on the first
page. Reproduction for commercial purposes is strictly prohibited
without the prior written consent of the Internet Society, the
first-named author (for reproduction of an entire paper only), and
the
Bugzilla
CVE-2016-5129 chromium-browser: memory corruption in v8
bugzilla·2016-07-21·CVSS 8.8
CVE-2016-5129 [HIGH] CVE-2016-5129 chromium-browser: memory corruption in v8
CVE-2016-5129 chromium-browser: memory corruption in v8
A memory corruption flaw was found in the V8 component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=620553
External References:
https://googlechromereleases.blogspot.com/2016/07/stable-channel-update.html
Discussion:
This issue has been addressed in the following products:
Red Hat Enterprise Linux 6 Supplementary
Via RHSA-2016:1485 https://rhn.redhat.com/errata/RHSA-2016-1485.html
http://googlechromereleases.blogspot.com/2016/07/stable-channel-update.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-07/msg00020.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-07/msg00021.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-07/msg00022.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-07/msg00028.htmlhttp://rhn.redhat.com/errata/RHSA-2016-1485.htmlhttp://www.debian.org/security/2016/dsa-3637http://www.securityfocus.com/bid/92053http://www.securitytracker.com/id/1036428http://www.securitytracker.com/id/1038201http://www.ubuntu.com/usn/USN-3041-1https://codereview.chromium.org/2078403002/https://codereview.chromium.org/2102243002https://codereview.chromium.org/2111133002https://crbug.com/620553https://security.gentoo.org/glsa/201610-09https://source.android.com/security/bulletin/2017-04-01http://googlechromereleases.blogspot.com/2016/07/stable-channel-update.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-07/msg00020.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-07/msg00021.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-07/msg00022.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-07/msg00028.htmlhttp://rhn.redhat.com/errata/RHSA-2016-1485.htmlhttp://www.debian.org/security/2016/dsa-3637http://www.securityfocus.com/bid/92053http://www.securitytracker.com/id/1036428http://www.securitytracker.com/id/1038201http://www.ubuntu.com/usn/USN-3041-1https://codereview.chromium.org/2078403002/https://codereview.chromium.org/2102243002https://codereview.chromium.org/2111133002https://crbug.com/620553https://security.gentoo.org/glsa/201610-09https://source.android.com/security/bulletin/2017-04-01
2016-07-23
Published