Application crash via null AVC configuration dereference
Published Jan 3, 2024 · Updated Jun 18, 2025
Null-pointer dereference in GPAC MP4Box 2.3-DEV-rev605-gfc9e29089-master allows attackers to crash the application with crafted media. The gf_avc_change_vui function accepts a null AVC configuration pointer and later dereferences it instead of rejecting the noncompliant bitstream. The published proof of concept requires MP4Box to import an attacker-controlled file, and the demonstrated consequence is a process abort.
Summary
What happened
Null-pointer dereference in GPAC MP4Box 2.3-DEV-rev605-gfc9e29089-master allows attackers to crash the application with crafted media. The gf_avc_change_vui function accepts a null AVC configuration pointer and later dereferences it instead of rejecting the noncompliant bitstream. The published proof of concept requires MP4Box to import an attacker-controlled file, and the demonstrated consequence is a process abort.
The record
- CVE
- CVE-2023-46929
- Published
- Jan 3, 2024
- Updated
- Jun 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 3, 2024CVE publishedPublication date reported by the CVE source.
- Jun 18, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Public exploit references
- poc2gpac MP4Box crash proof of conceptproof of concept · demonstrated
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