Bento4 Vulnerabilities

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Last Year

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Version

1.6.0-63935
1.5.1.016
1.5.1-62416
1.5.1-62712
1.5.0-61710

Grouping all affected versions of a specific product helps to determine existing issues. This makes it possible to determine vendors and products which need attention when it comes to remediations.

Remediation

Official Fix7
Temporary Fix0
Workaround0
Unavailable0
Not Defined130

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability

High0
Functional0
Proof-of-Concept24
Unproven0
Not Defined113

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector

Not Defined0
Physical0
Local13
Adjacent39
Network85

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication

Not Defined0
High0
Low41
None96

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction

Not Defined0
Required69
None68

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Last Year

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base

≤10
≤20
≤30
≤413
≤535
≤636
≤723
≤827
≤93
≤100

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp

≤10
≤20
≤30
≤415
≤534
≤636
≤725
≤824
≤93
≤100

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB

≤10
≤20
≤30
≤438
≤533
≤626
≤725
≤815
≤90
≤100

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD

≤10
≤20
≤30
≤40
≤50
≤623
≤746
≤822
≤920
≤103

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

CNA

≤10
≤20
≤30
≤40
≤57
≤63
≤73
≤84
≤90
≤100

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day

<1k47
<2k69
<5k21
<10k0
<25k0
<50k0
<100k0
≥100k0

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today

<1k124
<2k10
<5k3
<10k0
<25k0
<50k0
<100k0
≥100k0

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Last Year

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Versions (14): 1.2, 1.5.0-616, 1.5.0-617, 1.5.1, 1.5.1-624, 1.5.1-627, 1.5.1-628, 1.6, 1.6.0-636, 1.6.0-637, 1.6.0-638, 1.6.0-639, 5e7bb34, 06c39d9

Software Type: Multimedia Player Software

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
10/30/20234.94.8Axiomatic Bento4 Ap4File.cpp ParseStream null pointer dereference$0-$5k$0-$5kProof-of-ConceptNot Defined0.03CVE-2022-41841
08/23/20235.55.5Axiomatic Bento4 mp4encrypt ProcessFragments memory corruption$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2023-38666
04/21/20234.54.4Axiomatic Bento4 mp42aac memory leak$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2023-29575
04/14/20233.53.5Axiomatic Bento4 mp4info resource consumption$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2023-29573
04/12/20233.53.5Axiomatic Bento4 mp42avc resource consumption$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2023-29574
04/12/20235.55.4Axiomatic Bento4 Ap4TrunAtom.h SetDataOffset(int memory corruption$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2023-29576
12/17/20227.16.9Axiomatic Bento4 mp42aac heap-based overflow$0-$5k$0-$5kProof-of-ConceptNot Defined0.07CVE-2022-4584
11/13/20226.35.7Axiomatic Bento4 mp4info Ap4StdCFileByteStream.cpp ReadPartial heap-based overflow$0-$5k$0-$5kProof-of-ConceptNot Defined0.00CVE-2022-3974
11/01/20225.04.9Axiomatic Bento4 mp4mux memory leak$0-$5k$0-$5kProof-of-ConceptNot Defined0.00CVE-2022-3817
11/01/20224.33.9Axiomatic Bento4 mp4decrypt memory leak$0-$5k$0-$5kProof-of-ConceptNot Defined0.04CVE-2022-3816
11/01/20225.04.9Axiomatic Bento4 mp4decrypt memory leak$0-$5k$0-$5kProof-of-ConceptNot Defined0.00CVE-2022-3815
11/01/20225.04.9Axiomatic Bento4 mp4decrypt memory leak$0-$5k$0-$5kProof-of-ConceptNot Defined0.06CVE-2022-3814
11/01/20224.33.9Axiomatic Bento4 mp4edit memory leak$0-$5k$0-$5kProof-of-ConceptNot Defined0.00CVE-2022-3813
11/01/20225.04.9Axiomatic Bento4 mp4encrypt AP4_ContainerAtom memory leak$0-$5k$0-$5kProof-of-ConceptNot Defined0.02CVE-2022-3812
11/01/20225.04.9Axiomatic Bento4 mp42hevc Mp42Hevc.cpp AP4_File denial of service$0-$5k$0-$5kProof-of-ConceptNot Defined0.04CVE-2022-3810
11/01/20225.04.9Axiomatic Bento4 mp4tag Mp4Tag.cpp ParseCommandLine denial of service$0-$5k$0-$5kProof-of-ConceptNot Defined0.02CVE-2022-3809
11/01/20225.04.9Axiomatic Bento4 Incomplete Fix CVE-2019-13238 resource consumption$0-$5k$0-$5kProof-of-ConceptNot Defined0.04CVE-2022-3807
10/31/20226.86.6Axiomatic Bento4 Avcinfo SetDataSize heap-based overflow$0-$5k$0-$5kProof-of-ConceptNot Defined0.04CVE-2022-3785
10/31/20226.86.6Axiomatic Bento4 mp4hls Ap4Mp4AudioInfo.cpp ReadBits heap-based overflow$0-$5k$0-$5kProof-of-ConceptNot Defined0.07CVE-2022-3784
10/22/20227.36.6Axiomatic Bento4 mp42hevc WriteSample heap-based overflow$0-$5k$0-$5kProof-of-ConceptNot Defined0.02CVE-2022-3670
10/22/20225.45.2Axiomatic Bento4 mp4edit Create memory leak$0-$5k$0-$5kProof-of-ConceptNot Defined0.04CVE-2022-3669
10/22/20225.45.2Axiomatic Bento4 mp4edit CreateAtomFromStream memory leak$0-$5k$0-$5kProof-of-ConceptNot Defined0.04CVE-2022-3668
10/22/20227.36.6Axiomatic Bento4 mp42aac Ap4ByteStream.cpp WritePartial heap-based overflow$0-$5k$0-$5kProof-of-ConceptNot Defined0.02CVE-2022-3667
10/22/20227.57.2Axiomatic Bento4 mp42ts Ap4LinearReader.cpp Advance use after free$0-$5k$0-$5kProof-of-ConceptNot Defined0.06CVE-2022-3666
10/22/20227.57.2Axiomatic Bento4 avcinfo AvcInfo.cpp heap-based overflow$0-$5k$0-$5kProof-of-ConceptNot Defined0.04CVE-2022-3665

112 more entries are not shown

Interested in the pricing of exploits?

See the underground prices here!