CVE-2025-25723
Published: 28 February 2025
Summary
CVE-2025-25723 is a high-severity Classic Buffer Overflow (CWE-120) vulnerability in Gpac Gpac. Its CVSS base score is 8.4 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Client Execution (T1203); ranked at the 20.1th 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 are NIST 800-53 SI-16 (Memory Protection) and SI-2 (Flaw Remediation).
Threat & Defense at a Glance
Threat & Defense Details
Mitigating Controls (NIST 800-53 r5)AI
Directly mandates timely identification, testing, and installation of patches to remediate the buffer overflow vulnerability in GPAC version 2.5.
Provides memory safeguards like non-executable memory and address space randomization to block arbitrary code execution from the buffer overflow exploit.
Requires vulnerability scanning that identifies the presence of CVE-2025-25723 in GPAC, enabling proactive remediation.
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Buffer overflow in GPAC (client multimedia framework) enables local arbitrary code execution with no privileges required, directly mapping to Exploitation for Client Execution.
NVD Description
Buffer Overflow vulnerability in GPAC version 2.5 allows a local attacker to execute arbitrary code.
Deeper analysisAI
CVE-2025-25723 is a buffer overflow vulnerability (CWE-120) in GPAC version 2.5. This flaw enables a local attacker to execute arbitrary code on affected systems running the vulnerable version of the GPAC multimedia framework.
The vulnerability can be exploited by a local attacker requiring only local access (AV:L), low attack complexity (AC:L), no privileges (PR:N), and no user interaction (UI:N), with an unchanged scope (S:U). Successful exploitation grants high impacts on confidentiality, integrity, and availability (C:H/I:H/A:H), as reflected in its CVSS 3.1 base score of 8.4.
Mitigation is available through a patch in the GPAC GitHub repository at commit 74e26b8dfeb0ab8c7317603b80a18306d0698473. Additional details on the issue are documented in GPAC GitHub issue #3089.
Details
- CWE(s)