CVE-2023-6349

Memory corruption via stale VP9 resize buffers

Published May 27, 2024 · Updated Aug 2, 2024

Heap-based buffer overflow in the VP9 encoder in Google libvpx 1.5.0 through 1.13.0 allows local users to corrupt memory during encoding. When frame dimensions exceed the original configuration, vp9_change_config retains buffers sized for the prior macroblock grid instead of reallocating them for the new geometry. Triggering the faulty path requires low-privileged access to supply dimensions to a VP9 encoding workflow, and the resulting out-of-bounds writes can crash the encoding process or corrupt its data.

CVSS severity5.7
Medium
EPSS probability0.36%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Heap-based buffer overflow in the VP9 encoder in Google libvpx 1.5.0 through 1.13.0 allows local users to corrupt memory during encoding. When frame dimensions exceed the original configuration, vp9_change_config retains buffers sized for the prior macroblock grid instead of reallocating them for the new geometry. Triggering the faulty path requires low-privileged access to supply dimensions to a VP9 encoding workflow, and the resulting out-of-bounds writes can crash the encoding process or corrupt its data.

The record

CVE
CVE-2023-6349
Published
May 27, 2024
Updated
Aug 2, 2024
Vendor
Google
Product
libvpx
Classifications
CWE-122, CAPEC-100, T1203
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. May 27, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 2, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=1.5.0 <1.13.1

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Google · libvpxversion=1.5.0 <1.13.1

Published CVSS scores

7.5NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
5.7GoogleCVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:P/VC:L/VI:H/VA:N/SC:L/SI:H/SA:N/S:N/AU:N/R:A/V:D

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-122Heap-based Buffer Overflow
CAPEC-100Overflow Buffers
T1203Exploitation for Client Execution

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo