CVE-2015-6792
What it is
The MIDI subsystem in Google Chrome before 47.0.2526.106 does not properly handle the sending of data, which allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via unspecified vectors, related to midi_manager.cc, midi_manager_alsa.cc, and midi_manager_mac.cc, a different vulnerability than CVE-2015-8664.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 4.0% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- ReservedThe CVE id was reserved by its CNA
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 4.0% in the next 30 days (EPSS).
- Severity: 9.8 CRITICAL (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 4.0% · EPSS, next 30 days
- Record status
- Modified
Affected
- Google Chrome ≤ 47.0.2526.80
Attack profile CVSS 3.0 · 9.8
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2015-6792.md and follow it. Check whether this project is affected by CVE-2015-6792. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- http://googlechromereleases.blogspot.com/2015/12/stable-channel-update_15.html
- http://lists.opensuse.org/opensuse-security-announce/2015-12/msg00029.html
- http://lists.opensuse.org/opensuse-security-announce/2015-12/msg00030.html
- http://rhn.redhat.com/errata/RHSA-2015-2665.html
- http://www.debian.org/security/2016/dsa-3456
- http://www.securityfocus.com/bid/79348
- http://www.securitytracker.com/id/1034491
- https://code.google.com/p/chromium/issues/detail?id=564501
- https://code.google.com/p/chromium/issues/detail?id=569486
- https://codereview.chromium.org/1500153002
- https://codereview.chromium.org/1508563003
- https://security.gentoo.org/glsa/201603-09
- http://googlechromereleases.blogspot.com/2015/12/stable-channel-update_15.html
- http://lists.opensuse.org/opensuse-security-announce/2015-12/msg00029.html
- http://lists.opensuse.org/opensuse-security-announce/2015-12/msg00030.html
- http://rhn.redhat.com/errata/RHSA-2015-2665.html
- http://www.debian.org/security/2016/dsa-3456
- http://www.securityfocus.com/bid/79348
- http://www.securitytracker.com/id/1034491
- https://code.google.com/p/chromium/issues/detail?id=564501
- https://code.google.com/p/chromium/issues/detail?id=569486
- https://codereview.chromium.org/1500153002
- https://codereview.chromium.org/1508563003
- https://security.gentoo.org/glsa/201603-09