CVE-2022-3666 json
Axiomatic Bento4 mp42ts Ap4LinearReader.cpp Advance use after free
published 4y ago modified 4mo ago also EUVD-2022-43025
- cvss
- 7.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 0
- none known
Summary
A vulnerability, which was classified as critical, has been found in Axiomatic Bento4. Affected by this issue is the function AP4_LinearReader::Advance of the file Ap4LinearReader.cpp of the component mp42ts. The manipulation leads to use after free. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. VDB-212006 is the identifier assigned to this vulnerability.
Is CVE-2022-3666 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
0.87% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/axiomatic-systems/Bento4/issues/793 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/axiomatic-systems/Bento4/files/9744391/mp42ts_poc.zip 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.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- Axiomatic Bento4
Classification
References
-
github.com
/axiomatic-systems/Bento4/issues/793
exploit, third-party-advisory
-
github.com
/axiomatic-systems/Bento4/files/9744391/mp42ts_poc.zip
exploit, third-party-advisory
-
vuldb.com
/?id.212006
permissions-required, third-party-advisory
Sources
- CVE List CVE-2022-3666
- NVD CVE-2022-3666
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.