Secuno
ENNL
Book demo

CVE-2024-24267

Gpac vulnerability

7.5 HIGHPublic exploitEPSS 1.64%
  1. Published5 Feb 2024

Description

gpac v2.2.1 (fixed in v2.4.0) was discovered to contain a memory leak via the gfio_blob variable in the gf_fileio_from_blob function.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityNone
IntegrityNone
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

Gpac≥ 2.2.1 < 2.4.0

Remediation

Fixed in
Gpac≥ 2.4.0

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-870789.1
Net::IDN::Punycode versions from 2.302 before 2.590 for Perl leak the output buffer on…
CVE-2026-514008.4
An issue in Vim Project v9.2.0389 and earlier allows a local attacker to execute…
CVE-2026-129328.1
A memory leak in the tls-crypt-v2 client key extraction in OpenVPN 2.5.0 through 2.6.20…
CVE-2026-641048.7
In the Linux kernel, the following vulnerability has been resolved: virt: sev-guest:…
CVE-2026-463038.2
In the Linux kernel, the following vulnerability has been resolved: isofs: validate…
CVE-2026-462899.8
In the Linux kernel, the following vulnerability has been resolved: lib/scatterlist:…

Frequently asked

Is CVE-2024-24267 being actively exploited?

CVE-2024-24267 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 1.64%.

How severe is CVE-2024-24267?

CVE-2024-24267 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 1.64% probability of exploitation.

Which products are affected by CVE-2024-24267?

Affected products include Gpac.

How do I fix CVE-2024-24267?

Upgrade affected software to a fixed version, for example Gpac 2.4.0 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-24267 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.