Cyber Resilience

CVE-2024-6061

DoS in Gpac 2.5-dev-rev288-g11067ea92-master

Public PoCDoS
Published
17 June 2024
Modified
21 November 2024
Patch / advisory
CVSS Score v4 4.8
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0035 28th percentile
Risk Priority 26 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-6061 is a medium-severity Infinite Loop (CWE-835) vulnerability in Gpac Gpac. Its CVSS base score is 4.8 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 28th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

A vulnerability has been found in GPAC 2.5-DEV-rev228-g11067ea92-master and classified as problematic. Affected by this vulnerability is the function isoffin_process of the file src/filters/isoffin_read.c of the component MP4Box. The manipulation leads to infinite loop. It is possible to launch the…

more

attack on the local host. The exploit has been disclosed to the public and may be used. The identifier of the patch is 20c0f29139a82779b86453ce7f68d0681ec7624c. It is recommended to apply a patch to fix this issue. The identifier VDB-268789 was assigned to this vulnerability.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-50120Same product: Gpac Gpac
CVE-2023-47384Same product: Gpac Gpac
CVE-2023-23145Same product: Gpac Gpac
CVE-2023-48090Same product: Gpac Gpac
CVE-2023-48039Same product: Gpac Gpac
CVE-2023-48958Same product: Gpac Gpac
CVE-2024-24267Same product: Gpac Gpac
CVE-2023-46871Same product: Gpac Gpac
CVE-2024-24265Same product: Gpac Gpac
CVE-2024-50665Same product: Gpac Gpac

Affected Assets

gpac
gpac
2.5-dev-rev288-g11067ea92-master

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover unreachable loop exit conditions through static analysis, fuzzing, or execution tracing.

Flaw remediation processes identify and correct infinite-loop defects reported from testing or operations.

Requiring documented development processes and secure coding standards reduces introduction of loops whose termination conditions are unreachable.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices (reviews, testing, static analysis) directly prevent introduction of infinite-loop defects.

ID.RA-01 partial match
prevents

Static analysis and vuln scanning during asset assessment can detect unreachable loop exits.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can uncover infinite-loop conditions before release.

prevents

Secure development life cycle mandates practices that can detect and prevent infinite-loop defects.

prevents

Application security requirements can specify loop-termination rules, indirectly reducing the weakness.

prevents

Secure coding standards directly address loop termination and prevent infinite loops.

References