CVE-2023-3291 | Heap-based Buffer Overflow in gpac/gpac

Exp

Heap-based Buffer Overflow in GitHub repository gpac/gpac prior to 2.2.2.

Published: 2023-06-16 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-3291 is rated Exploit Available (50/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.38%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2023-3291

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2023-3291

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.06% 0.38% +0.32%
2 2025-03-30 0.16% 0.06% -0.10%
3 2025-03-29 — 0.16% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-3291

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.3 3.1 LOW
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.8 1.4 [email protected]
5.1 3.0 MEDIUM
CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 2.5 2.5 [email protected]

Weakness enumeration for CVE-2023-3291

OS Trackers for CVE-2023-3291

vendor priority summary link
debian end-of-life CVE-2023-3291 end-of-life priority: Debian including 1 source packages (gpac), 1 status rows across 1 suites (bullseye): open 1. https://security-tracker.debian.org/tracker/CVE-2023-3291
ubuntu medium CVE-2023-3291 medium priority: Ubuntu including 1 source packages (gpac), 13 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): needs-triage 7, DNE 4, ignored 2. https://ubuntu.com/security/CVE-2023-3291

Affected software / configurations for CVE-2023-3291

Vendor Product Version Raw CPE
gpac gpac < 2.2.2 cpe:2.3:a:gpac:gpac:*:*:*:*:*:*:*:*

References for CVE-2023-3291

cvelogic Threat Intelligence