CVE-2018-6129
published 2019-06-27CVE-2018-6129: Out of bounds array access in WebRTC in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to potentially perform out of bounds memory access via a…
PriorityP340medium6.5CVSS 3.0
AVNACLPRNUIRSUCNINAH
EXPLOIT
EPSS
2.75%
84.3th percentile
Out of bounds array access in WebRTC in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| chrome | < 67.0.3396.62 | 67.0.3396.62 | |
| chrome | >= unspecified < 67.0.3396.62 | 67.0.3396.62 |
CVSS provenance
nvdv3.06.5MEDIUMCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:N/I:N/A:P
osv6.5MEDIUM
vendor_redhat6.5MEDIUM
CVEs like this are exactly what “Exploited This Week” covers.
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.
GHSA
GHSA-cgw7-3f4w-4c8f: Out of bounds array access in WebRTC in Google Chrome prior to 67
ghsa_unreviewed·2022-05-24
CVE-2018-6129 [MEDIUM] CWE-125 GHSA-cgw7-3f4w-4c8f: Out of bounds array access in WebRTC in Google Chrome prior to 67
Out of bounds array access in WebRTC in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page.
OSV
CVE-2018-6129: Out of bounds array access in WebRTC in Google Chrome prior to 67
osv·2019-06-27·CVSS 6.5
CVE-2018-6129 [MEDIUM] CVE-2018-6129: Out of bounds array access in WebRTC in Google Chrome prior to 67
Out of bounds array access in WebRTC in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page.
Project0
Adventures in Video Conferencing Part 1: The Wild World of WebRTC - Project Zero
project_zero·2018-12-01
CVE-2018-16071 Adventures in Video Conferencing Part 1: The Wild World of WebRTC - Project Zero
Posted by Natalie Silvanovich, Project Zero
Over the past five years, video conferencing support in websites and applications has exploded. Facebook, WhatsApp, FaceTime and Signal are just a few of the many ways that users can make audio and video calls across networks. While a lot of research has been done into the cryptographic and privacy properties of video conferencing, there is limited information available about the attack surface of these platforms and their susceptibility to vulnerabilities. We reviewed the three most widely-used video conferencing implementations. In this series of blog posts, we describe what we found.
This part will discuss our analysis of WebRTC. Part 2 will cover our analysis of FaceTime. Part 3 will discuss how we fuzzed WhatsApp. Part 4 will describe so
Red Hat
chromium-browser: Out of bounds memory access in WebRTC
vendor_redhat·2018-05-29·CVSS 6.5
CVE-2018-6129 [MEDIUM] chromium-browser: Out of bounds memory access in WebRTC
chromium-browser: Out of bounds memory access in WebRTC
Out of bounds array access in WebRTC in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page.
No detection rules found.
Bugzilla
VP9 Missing Frame Processing Out-of-Bounds Memory Access
bugzilla·2018-06-08·CVSS 6.5
[MEDIUM] VP9 Missing Frame Processing Out-of-Bounds Memory Access
VP9 Missing Frame Processing Out-of-Bounds Memory Access
Looks like Firefox 62 is affected by this exploit published today: https://www.exploit-db.com/exploits/44863/
Discussion:
And for added fun a second one https://www.exploit-db.com/exploits/44862/
---
Google Project Zero reports for these:
https://bugs.chromium.org/p/project-zero/issues/detail?id=1567
https://bugs.chromium.org/p/project-zero/issues/detail?id=1568
I don't have access to the Chromium bug reports to see what the fix looks like. Apparently the fix has been shipped in Chrome 67. But CVE-2018-6129 and CVE-2018-6130 don't appear to be disclosed yet either.
---
Link to the Chromium bug which probably/hopefully contains the fix https://bugs.chromium.org/p/chromium/issues/detail?id=838402
---
CVE-2018-6130 appears to
Bugzilla
CVE-2018-6123 CVE-2018-6124 CVE-2018-6125 CVE-2018-6126 CVE-2018-6127 CVE-2018-6129 CVE-2018-6130 CVE-2018-6131 CVE-2018-6132 CVE-2018-6133 CVE-2018-6134 CVE-2018-6135 CVE-2018-6136 CVE-2018-6137 CVE-
bugzilla·2018-05-30·CVSS 6.5
CVE-2018-6123 [MEDIUM] CVE-2018-6123 CVE-2018-6124 CVE-2018-6125 CVE-2018-6126 CVE-2018-6127 CVE-2018-6129 CVE-2018-6130 CVE-2018-6131 CVE-2018-6132 CVE-2018-6133 CVE-2018-6134 CVE-2018-6135 CVE-2018-6136 CVE-2018-6137 CVE-
CVE-2018-6123 CVE-2018-6124 CVE-2018-6125 CVE-2018-6126 CVE-2018-6127 CVE-2018-6129 CVE-2018-6130 CVE-2018-6131 CVE-2018-6132 CVE-2018-6133 CVE-2018-6134 CVE-2018-6135 CVE-2018-6136 CVE-2018-6137 CVE-2018-6138 ... chromium: various flaws [epel-7]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-7.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-l
Bugzilla
CVE-2018-6123 CVE-2018-6124 CVE-2018-6125 CVE-2018-6126 CVE-2018-6127 CVE-2018-6129 CVE-2018-6130 CVE-2018-6131 CVE-2018-6132 CVE-2018-6133 CVE-2018-6134 CVE-2018-6135 CVE-2018-6136 CVE-2018-6137 CVE-
bugzilla·2018-05-30·CVSS 6.5
CVE-2018-6123 [MEDIUM] CVE-2018-6123 CVE-2018-6124 CVE-2018-6125 CVE-2018-6126 CVE-2018-6127 CVE-2018-6129 CVE-2018-6130 CVE-2018-6131 CVE-2018-6132 CVE-2018-6133 CVE-2018-6134 CVE-2018-6135 CVE-2018-6136 CVE-2018-6137 CVE-
CVE-2018-6123 CVE-2018-6124 CVE-2018-6125 CVE-2018-6126 CVE-2018-6127 CVE-2018-6129 CVE-2018-6130 CVE-2018-6131 CVE-2018-6132 CVE-2018-6133 CVE-2018-6134 CVE-2018-6135 CVE-2018-6136 CVE-2018-6137 CVE-2018-6138 ... chromium: various flaws [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the releva
Bugzilla
CVE-2018-6129 chromium-browser: Out of bounds memory access in WebRTC
bugzilla·2018-05-30·CVSS 6.5
CVE-2018-6129 [MEDIUM] CVE-2018-6129 chromium-browser: Out of bounds memory access in WebRTC
CVE-2018-6129 chromium-browser: Out of bounds memory access in WebRTC
An out of bounds memory access flaw was found in the WebRTC component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=838672
External References:
https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html
Discussion:
Created chromium tracking bugs for this issue:
Affects: epel-7 [bug 1584060]
Affects: fedora-all [bug 1584059]
---
This issue has been addressed in the following products:
Red Hat Enterprise Linux 6 Supplementary
Via RHSA-2018:1815 https://access.redhat.com/errata/RHSA-2018:1815
2019-06-27
Published