CVE-2022-3667 json
Axiomatic Bento4 mp42aac Ap4ByteStream.cpp WritePartial heap-based overflow
published 4y ago modified 4mo ago also EUVD-2022-43026
- cvss
- 7.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
A vulnerability, which was classified as critical, was found in Axiomatic Bento4. This affects the function AP4_MemoryByteStream::WritePartial of the file Ap4ByteStream.cpp of the component mp42aac. The manipulation leads to heap-based buffer overflow. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-212007.
Is CVE-2022-3667 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
1.43% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/axiomatic-systems/Bento4/issues/789 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/17ssDP/fuzzer_crashes/blob/main/Bento4/mp42aac-hbo-01 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Axiomatic Bento4
Classification
References
-
github.com
/axiomatic-systems/Bento4/issues/789
exploit, third-party-advisory
-
github.com
/17ssDP/fuzzer_crashes/blob/main/Bento4/mp42aac-hbo-01
exploit, third-party-advisory
-
vuldb.com
/?id.212007
permissions-required, third-party-advisory
Sources
- CVE List CVE-2022-3667
- NVD CVE-2022-3667
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.