Security Resilience

CVE-2024-24265

Gpac 2.2.1

Public PoC
Published
05 February 2024
Modified
17 June 2026
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.013 71th percentile
Risk Priority 60 floored blend · peak EPSS

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

Summary

CVE-2024-24265 is a high-severity Missing Release of Memory after Effective Lifetime (CWE-401) vulnerability in Gpac. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked in the top 29% of CVEs by exploit likelihood; 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 SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

gpac v2.2.1 was discovered to contain a memory leak via the dst_props variable in the gf_filter_pid_merge_properties_internal function.

CWE(s)
CWE-401

Related Threats

MITRE ATT&CK Enterprise Techniques

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.
attack.mitre.org →
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.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-48958Same product: Gpac Gpac
CVE-2023-48090Same product: Gpac Gpac
CVE-2023-23145Same product: Gpac Gpac
CVE-2023-46871Same product: Gpac Gpac
CVE-2023-48039Same product: Gpac Gpac
CVE-2023-47384Same product: Gpac Gpac
CVE-2024-24267Same product: Gpac Gpac
CVE-2026-9572Same product: Gpac Gpac
CVE-2023-3291Same product: Gpac Gpac
CVE-2023-0841Same product: Gpac Gpac

Affected Assets

gpac
gpac
2.2.1

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation (static analysis, fuzzing, or runtime leak detection) directly finds missing deallocation.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented development standards and tools can mandate memory-management disciplines that avoid leaks at introduction.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles applied during development can require explicit resource-release patterns that stop memory leaks from being coded.

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
blocks

Secure SDLC practices directly enforce proper memory allocation/deallocation via coding standards, reviews, and tooling.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect unreleased memory, providing partial coverage of the weakness.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require proper allocation/deallocation, covering most of this weakness.

A.8.6 Capacity management partial match
finds

Capacity management may detect memory exhaustion symptoms but does not prevent the coding flaw.

References