Cyber Resilience

CVE-2023-42298

Memory Safety in Gpac ≤ 2.2.1

Memory Safety
Published
12 October 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0023 14th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2023-42298 is a medium-severity Integer Overflow or Wraparound (CWE-190) vulnerability in Gpac Gpac. Its CVSS base score is 5.5 (Medium).

Operationally, ranked at the 14th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

An issue in GPAC GPAC v.2.2.1 and before allows a local attacker to cause a denial of service via the Q_DecCoordOnUnitSphere function of file src/bifs/unquantize.c.

CWE(s)
CWE-190

Related Threats

CVEs Like This One

CVE-2023-4722Same product: Gpac Gpac
CVE-2023-23144Same product: Gpac Gpac
CVE-2025-55647Same product: Gpac Gpac
CVE-2026-1416Same product: Gpac Gpac
CVE-2026-1417Same product: Gpac Gpac
CVE-2023-4721Same product: Gpac Gpac
CVE-2025-25723Same product: Gpac Gpac
CVE-2025-60468Same product: Gpac Gpac
CVE-2024-6064Same product: Gpac Gpac
CVE-2025-55642Same product: Gpac Gpac

Affected Assets

gpac
gpac
≤ 2.2.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V5.2.6

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 directly require use of safe arithmetic, bounds checks, and testing that prevent integer overflows.

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
detects

Security testing in development can detect integer overflows before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates input validation and arithmetic checks that prevent integer overflows.

A.8.26 Application security requirements partial match
degrades

Application security requirements include bounds checking and safe arithmetic to avoid overflow conditions.

A.8.27 Secure system architecture and engineering principles partial match
degrades

Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe integer operations and mandate overflow-safe constructs.

References