CVE-2015-6761
What it is
The update_dimensions function in libavcodec/vp8.c in FFmpeg through 2.8.1, as used in Google Chrome before 46.0.2490.71 and other products, relies on a coefficient-partition count during multi-threaded operation, which allows remote attackers to cause a denial of service (race condition and memory corruption) or possibly have unspecified other impact via a crafted WebM file.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 1.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- 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: 1.1% in the next 30 days (EPSS).
- Severity: 6.8 MEDIUM (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 1.1% · EPSS, next 30 days
- Weakness
- CWE-362 · Race condition
- Record status
- Modified
Affected
- Ffmpeg ≤ 2.8.1
- Google Chrome ≤ 45.0.2454.101
Attack profile CVSS 2.0 · 6.8
- Attack vector
- Network
- Complexity
- Medium
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
Raw vector
AV:N/AC:M/Au:N/C:P/I:P/A:P
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-6761.md and follow it. Check whether this project is affected by CVE-2015-6761. 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://git.videolan.org/?p=ffmpeg.git%3Ba=commit%3Bh=dabea74d0e82ea80cd344f630497cafcb3ef872c
- http://googlechromereleases.blogspot.com/2015/10/stable-channel-update.html
- http://rhn.redhat.com/errata/RHSA-2015-1912.html
- http://www.debian.org/security/2015/dsa-3376
- http://www.securityfocus.com/bid/77073
- http://www.securitytracker.com/id/1033816
- http://www.ubuntu.com/usn/USN-2770-1
- http://www.ubuntu.com/usn/USN-2770-2
- https://code.google.com/p/chromium/issues/detail?id=447860
- https://code.google.com/p/chromium/issues/detail?id=532967
- https://codereview.chromium.org/1376913003
- https://lists.debian.org/debian-lts-announce/2018/12/msg00009.html
- https://security.gentoo.org/glsa/201603-09
- http://git.videolan.org/?p=ffmpeg.git%3Ba=commit%3Bh=dabea74d0e82ea80cd344f630497cafcb3ef872c
- http://googlechromereleases.blogspot.com/2015/10/stable-channel-update.html
- http://rhn.redhat.com/errata/RHSA-2015-1912.html
- http://www.debian.org/security/2015/dsa-3376
- http://www.securityfocus.com/bid/77073
- http://www.securitytracker.com/id/1033816
- http://www.ubuntu.com/usn/USN-2770-1
- http://www.ubuntu.com/usn/USN-2770-2
- https://code.google.com/p/chromium/issues/detail?id=447860
- https://code.google.com/p/chromium/issues/detail?id=532967
- https://codereview.chromium.org/1376913003
- https://lists.debian.org/debian-lts-announce/2018/12/msg00009.html