Buffer Overflow vulnerability infaad2 v.2.10.1 allows a remote attacker to execute arbitrary code and cause a denial of service via the mp4info function in mp4read.c:1039.
Product
faad2 project faad2 vulnerabilities
9 published CVES affecting faad2 project faad2, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 9
- Critical
- 0
- High
- 6
- Medium
- 3
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest faad2 project faad2 CVEs
Newest publication first
-
MediumCVSS 6.5 EPSS 1.0%
-
MediumCVSS 5.5 EPSS 0.59%
Buffer Overflow vulnerability infaad2 v.2.10.1 allows a remote attacker to execute arbitrary code and cause a denial of service via the stcoin function in mp4read.c.
-
HighCVSS 7.8 EPSS 1.3%
An issue was discovered in faad2 through 2.10.0. A heap-buffer-overflow exists in the function sbr_qmf_analysis_32 located in sbr_qmf.c. It allows an attacker to cause code Execution.
-
MediumCVSS 5.5 EPSS 0.88%
An issue was discovered in faad2 through 2.10.0. A NULL pointer dereference exists in the function get_sample() located in output.c. It allows an attacker to cause Denial of Service.
-
HighCVSS 7.8 EPSS 1.3%
An issue was discovered in faad2 through 2.10.0. A heap-buffer-overflow exists in the function sbr_qmf_synthesis_64 located in sbr_qmf.c. It allows an attacker to cause code Execution.
-
HighCVSS 7.8 EPSS 1.3%
An issue was discovered in faad2 before 2.10.0. A heap-buffer-overflow exists in the function stszin located in mp4read.c. It allows an attacker to cause Code Execution.
-
HighCVSS 7.8 EPSS 1.3%
An issue was discovered in faad2 through 2.10.0. A heap-buffer-overflow exists in the function lt_prediction located in lt_predict.c. It allows an attacker to cause code Execution.
-
HighCVSS 7.8 EPSS 1.2%
An issue was discovered in faad2 through 2.10.0. A stack-buffer-overflow exists in the function ftypin located in mp4read.c. It allows an attacker to cause Code Execution.
-
HighCVSS 7.8 EPSS 1.1%
Stack-based buffer overflow vulnerability in frontend/main.c in faad2 before 2.2.7.1 allow local attackers to execute arbitrary code via filename and pathname options.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.