Gpac 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.0.185
0.8.033
1.1.030
0.7.114
0.9.0-development-2019110913

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 Fix83
Temporary Fix0
Workaround0
Unavailable0
Not Defined121

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-Concept1
Unproven0
Not Defined203

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
Local31
Adjacent150
Network23

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
Low154
None50

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
Required42
None162

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
≤31
≤478
≤553
≤640
≤726
≤83
≤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
≤31
≤479
≤552
≤647
≤719
≤83
≤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
≤31
≤4133
≤55
≤652
≤78
≤85
≤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
≤661
≤73
≤828
≤90
≤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
≤31
≤41
≤50
≤64
≤70
≤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

<1k131
<2k27
<5k46
<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

<1k176
<2k28
<5k0
<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 (28): 0.1, 0.2, 0.3, 0.4, 0.5, 0.5.2, 0.6, 0.7, 0.7.1, 0.7.2, 0.8, 0.8.0-rev177-g51a8ef874-master, 0.9.0-development-20191109, 1, 1.0, 1.0.1, 1.0.2, 1.1, 1.1.0-DEV-rev1663-g881c6a94a-master, 1.1.0-DEV-rev1727-g8be34973d-master, 1.1.0-DEV-rev1759-geb2d1e6dd, 2, 2.0, 2.1-DEV, 2.1-DEV-rev87-g053aae8-master, 2.1-DEV-rev232-gfcaa01ebb-master, 4.c, 20200801

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
09/15/20224.24.1GPAC recursion$0-$5k$0-$5kNot DefinedOfficial Fix0.08CVE-2022-3222
09/13/20227.06.9gpac buffer over-read$0-$5k$0-$5kNot DefinedOfficial Fix0.07CVE-2022-3178
09/07/20225.55.5GPAC ISOM_IOD stack-based overflow$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2022-38530
08/17/20225.55.4GPAC MP4Box avc_ext.c gf_isom_dovi_config_get heap-based overflow$0-$5k$0-$5kNot DefinedOfficial Fix0.06CVE-2022-36191
08/17/20225.55.3GPAC MP4Box gf_isom_dovi_config_get use after free$0-$5k$0-$5kNot DefinedOfficial Fix0.07CVE-2022-36190
08/17/20223.53.4GPAC filter_pid.c gf_filter_pid_set_property_full null pointer dereference$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-36186
07/27/20224.94.9GPAC null pointer dereference$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2022-2549
07/20/20227.37.2GPAC integer overflow$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2022-2454
07/20/20227.37.2GPAC use after free$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2022-2453
06/29/20224.54.5GPAC MP4Box filter_pid.c gf_filter_pid_get_packet denial of service$0-$5k$0-$5kNot DefinedNot Defined0.06CVE-2021-40944
06/29/20224.54.5GPAC MP4Box GetHintFormat denial of service$0-$5k$0-$5kNot DefinedNot Defined0.03CVE-2021-40609
06/29/20224.54.5GPAC MP4Box gf_hinter_track_finalize denial of service$0-$5k$0-$5kNot DefinedNot Defined0.03CVE-2021-40608
06/29/20224.54.5GPAC MP4Box schm_box_size denial of service$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2021-40607
06/29/20224.54.5GPAC gf_bs_write_data denial of service$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2021-40606
06/28/20224.54.5GPAC MP4Box filter.c filter_parse_dyn_args denial of service$0-$5k$0-$5kNot DefinedNot Defined0.03CVE-2021-40942
06/16/20223.53.5GPAC MP4Box error.c stack-based overflow$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2021-41458
06/09/20223.53.4GPAC ISOBMFF Reader Filter isoffin_read.c isoffin_process infinite loop$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2021-40592
05/19/20226.16.0GPAC use after free$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-1795
05/18/20225.55.5GPAC utf.c utf8_wcslen heap-based overflow$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2022-30976
05/05/20223.53.4GPAC gf_isom_parse_movie_boxes_internal null pointer dereference$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2022-29340
05/05/20223.53.4GPAC bitstream.c BS_ReadByte denial of service$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-29339
04/26/20226.36.0GPAC MP4Box diST_box_read memory corruption$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2022-1441
04/21/20225.55.5GPAC rtp_pck_mpeg4.c gp_rtp_builder_do_hevc heap-based overflow$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2022-29537
04/08/20225.55.5GPAC MP4Box integer overflow$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2022-27148
04/08/20225.55.5GPAC MP4Box gf_node_get_attribute_by_tag use after free$0-$5k$0-$5kNot DefinedNot Defined0.03CVE-2022-27147

179 more entries are not shown

Might our Artificial Intelligence support you?

Check our Alexa App!