How severe is CVE-2024-42011?

CVE-2024-42011 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2024-42011 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (44th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2024-42011?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2024-42011 have an EU (EUVD) identifier?

Yes. CVE-2024-42011 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-39393.

When was CVE-2024-42011 published?

CVE-2024-42011 was published on 2024-10-28 and last updated on 2026-06-17.

CVE-2024-42011

CVE-2024-42011 is a high-severity vulnerability with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-120.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 1% (44th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2024-39393
Weakness: CWE-120
Published: 2024-10-28
Last modified: 2026-06-17

Description

The Spotify app 8.9.58 for iOS has a buffer overflow in its use of strcat.

Frequently asked questions

What is CVE-2024-42011?: The Spotify app 8.9.58 for iOS has a buffer overflow in its use of strcat.
How severe is CVE-2024-42011?: CVE-2024-42011 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2024-42011 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (44th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2024-42011?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2024-42011 have an EU (EUVD) identifier?: Yes. CVE-2024-42011 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-39393.
When was CVE-2024-42011 published?: CVE-2024-42011 was published on 2024-10-28 and last updated on 2026-06-17.

References

Other CWE-120 (Classic Buffer Overflow) vulnerabilities

CVE-2025-48611 — Critical (CVSS 10.0): In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead…
CVE-2026-24823 — Critical (CVSS 10.0): Out-of-bounds Write, Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in FASTSHIFT…
CVE-2026-24810 — Critical (CVSS 10.0): Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in rethinkdb (src/cjson modules).…
CVE-2026-24800 — Critical (CVSS 10.0): Out-of-bounds Write, Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in tildearrow…
CVE-2025-9962 — Critical (CVSS 10.0): A buffer overflow vulnerability in Novakon P series allows attackers to gain root permission without prior…
CVE-2010-10016 — Critical (CVSS 10.0): BS.Player version 2.57 (build 1051) contains a vulnerability in its playlist import functionality. When processing .m3u…

Browse all CWE-120 (Classic Buffer Overflow) vulnerabilities →