CVE-2018-0487: ARM mbed TLS before 1.3.22, before 2.1.10, and before 2.7.0 allows remote attackers to execute arbitrary code or cause a denial of service…
Noroxi assessment
Priority: Plan (action score 40/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 3.2% (FIRST EPSS); higher than 88.5% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: mbedtls (Alpine:v3.10) 2.7.0-r0; mbedtls2 (Alpine:v3.20) 2.7.0-r0; mbedtls3 (Alpine:v3.24) 2.7.0-r0.
Add it to your regular patch cycle. Upgrade to mbedtls (Alpine:v3.10) 2.7.0-r0; mbedtls2 (Alpine:v3.20) 2.7.0-r0; mbedtls3 (Alpine:v3.24) 2.7.0-r0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
ARM mbed TLS before 1.3.22, before 2.1.10, and before 2.7.0 allows remote attackers to execute arbitrary code or cause a denial of service (buffer overflow) via a crafted certificate chain that is mishandled during RSASSA-PSS signature verification within a TLS or DTLS session.
- Published
- Feb 13, 2018
- Updated
- Jun 16, 2026
- EPSS
- 3.2% · 88th percentile
- CWE
- CWE-119
Report tools
Action score
40
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Check your server's TLS configurationRun the SSL check
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
Check your server's TLS configuration
The Mbed TLS version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.
Run the SSL checkVersions reported by the vendor
Affected version ranges reported by the assigning authority (debian). Independent of NVD's CPE analysis and usually ahead of it.
n/a ARM mbed TLS before 1.3.22, before 2.1.10, and before 2.7.0
- ARM mbed TLS before 1.3.22, before 2.1.10, and before 2.7.0affected
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- arm mbed tls1.3.8 and later · before 1.3.22
- arm mbed tls2.1.0 and later · before 2.1.10
- arm mbed tls2.2.0 and later · before 2.7.0
- debian debian linux8.0
- debian debian linux9.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | mbedtls | before 2.7.0-r0 | 2.7.0-r0 |
| Alpine:v3.20 | mbedtls2 | before 2.7.0-r0 | 2.7.0-r0 |
| Alpine:v3.24 | mbedtls3 | before 2.7.0-r0 | 2.7.0-r0 |
| Debian:12 | mbedtls | before 2.7.0-2 | 2.7.0-2 |
| Debian:8 | polarssl | before 1.3.9-2.1+deb8u3 | 1.3.9-2.1+deb8u3 |
| Debian:9 | mbedtls | before 2.4.2-1+deb9u2 | 2.4.2-1+deb9u2 |
| openSUSE:Tumbleweed | mbedtls-2 | before 2.27.0-1.2 | 2.27.0-1.2 |
| openSUSE:Tumbleweed | mbedtls-3 | before 3.6.6-1.1 | 3.6.6-1.1 |
| SUSE:Package Hub 12 | mbedtls | before 1.3.19-11.1 | 1.3.19-11.1 |
Same product
arm: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-47917Mbed TLS before 3.6.4 allows a use-after-free in certain situations of applications that are developed in accordance with the documentation.40Plan
- CVE-2021-44732Mbed TLS before 3.0.1 has a double free in certain out-of-memory conditions, as demonstrated by an mbedtls_ssl_set_session() failure.40Plan
- CVE-2017-18187In ARM mbed TLS before 2.7.0, there is a bounds-check bypass through an integer overflow in PSK identity parsing in the…40Plan
Published before and after this one in the same product
- ← EarlierCVE-2017-14032Aug 30, 2017 · ARM mbed TLS before 1.3.21 and 2.x before 2.1.9, if optional authentication is configured, allows remote attackers to bypass peer…32Monitor
- Later →CVE-2018-0488Feb 13, 2018 · ARM mbed TLS before 1.3.22, before 2.1.10, and before 2.7.0, when the truncated HMAC extension and CBC are used, allows remote attackers to…40Plan
- Later →CVE-2018-9988Apr 10, 2018 · ARM mbed TLS before 2.1.11, before 2.7.2, and before 2.8.0 has a buffer over-read in ssl_parse_server_key_exchange() that could cause a…31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:mbedtls | 2.7.0-r0 · Alpine:v3.10 | Package registry (OSV) |
| alpine:mbedtls2 | 2.7.0-r0 · Alpine:v3.20 | Package registry (OSV) |
| alpine:mbedtls3 | 2.7.0-r0 · Alpine:v3.24 | Package registry (OSV) |
| debian:mbedtls | 2.7.0-2 · Debian:12 | Package registry (OSV) |
| debian:polarssl | 1.3.9-2.1+deb8u3 · Debian:8 | Package registry (OSV) |
| opensuse:mbedtls-2 | 2.27.0-1.2 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:mbedtls-3 | 3.6.6-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:mbedtls | 1.3.19-11.1 · SUSE:Package Hub 12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.