cve.bz

CVE-2024-28960 Improper Access Control

8.2 highEPSS 0.8%

High (8.2). EPSS 0.8% estimated probability of exploitation activity in the next 30 days.

On this page
An issue was discovered in Mbed TLS 2.18.0 through 2.28.x before 2.28.8 and 3.x before 3.6.0, and Mbed Crypto. The PSA Crypto API mishandles shared memory.

Severity

CVSS 3.1

8.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 59th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2024-05-02. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-284 Improper Access Control
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-28960 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-28960?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-28960?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-28960 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
arm:mbed_cryptothrough 3.1.0
arm:mbed_tlsfrom 2.1.8 before 2.28.8
trustedfirmware:mbed_tlsfrom 3.0.0 before 3.6.0
fedoraproject:fedora38
fedoraproject:fedora39
fedoraproject:fedora40

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12mbedtlsno fix listedDEBIAN-CVE-2024-28960
Debian13, 14mbedtls2.28.8-1DEBIAN-CVE-2024-28960
UbuntuPro:22.04:LTSmbedtlsno fix listedUBUNTU-CVE-2024-28960
openSUSETumbleweedmbedtls-22.28.8-1.1openSUSE-SU-2024:13813-1
Alpinev3.16, v3.17, v3.18 and 1 morembedtls2.28.8-r0ALPINE-CVE-2024-28960
Alpinev3.20, v3.21, v3.22 and 1 morembedtls, mbedtls22.28.8-r0ALPINE-CVE-2024-28960
Alpinev3.24mbedtls, mbedtls2, mbedtls32.28.8-r0ALPINE-CVE-2024-28960
Azure Linux2hvloader1.0.1-6AZL-47703

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpine.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability affects products that use Mbed TLS to provide an implementation of the PSA Crypto API with domain isolation between API callers (“client application”) and the API implementation (“crypto server”), where communication is done through shared memory. Applications that use Mbed TLS as a library inside their own process space are not affected.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2024-28960.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).

References

Check your stackJSON