Secuno
ENNL
Book demo

CVE-2024-36600

Gnu Libcdio buffer overflow

8.4 HIGHPublic exploitEPSS 0.36%
  1. Published14 Jun 2024

Description

Buffer Overflow Vulnerability in libcdio 2.2.0 (fixed in 2.3.0) allows an attacker to execute arbitrary code via a crafted ISO 9660 image file.

CVSS 3.1 breakdown

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

Affected products

Gnu Libcdio≥ 2.2.0 < 2.3.0

Remediation

Fixed in
Gnu Libcdio≥ 2.3.0

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-10910910.0
A vulnerability was detected in Wavlink WL-WN530BE1-A 251117. This vulnerability…
CVE-2026-854578.1
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to…
CVE-2026-962668.2
IBM Power Systems Firmware FW1060.00 through FW1060.81 is affected by a vulnerability…
CVE-2026-962648.2
IBM Power Systems Firmware FW1060.00 through FW1060.81 is affected by a vulnerability…
CVE-2026-962638.2
IBM Power Systems Firmware FW1120.00 through FW1120.01, FW1110.00 through FW1110.31,…
CVE-2026-962628.2
IBM Power Systems Firmware FW1060.00 through FW1060.81 is affected by a vulnerability…

Frequently asked

Is CVE-2024-36600 being actively exploited?

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

How severe is CVE-2024-36600?

CVE-2024-36600 has a CVSS 3.1 base score of 8.4, rated high. EPSS estimates a 0.36% probability of exploitation.

Which products are affected by CVE-2024-36600?

Affected products include Gnu Libcdio.

How do I fix CVE-2024-36600?

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

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-36600 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.