CVE-2018-0498: ARM mbed TLS before 2.12.0, before 2.7.5, and before 2.1.14 allows local users to achieve partial plaintext recovery (for a CBC based…
Noroxi assessment
Priority: Monitor (action score 18/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: 0.37% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: mbedtls (Alpine:v3.10) 2.12.0-r0; mbedtls2 (Alpine:v3.20) 2.12.0-r0; mbedtls3 (Alpine:v3.24) 2.12.0-r0.
Low priority for now. Upgrade to mbedtls (Alpine:v3.10) 2.12.0-r0; mbedtls2 (Alpine:v3.20) 2.12.0-r0; mbedtls3 (Alpine:v3.24) 2.12.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 2.12.0, before 2.7.5, and before 2.1.14 allows local users to achieve partial plaintext recovery (for a CBC based ciphersuite) via a cache-based side-channel attack.
- Published
- Jul 28, 2018
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 31th percentile
- CWE
- —
Report tools
Action score
18
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
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 2.12.0, before 2.7.5, and before 2.1.14
- ARM mbed TLS before 2.12.0, before 2.7.5, and before 2.1.14affected
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 tlsbefore 2.1.14
- arm mbed tls2.2.0 and later · before 2.7.5
- arm mbed tls2.8.0 and later · before 2.12.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.12.0-r0 | 2.12.0-r0 |
| Alpine:v3.20 | mbedtls2 | before 2.12.0-r0 | 2.12.0-r0 |
| Alpine:v3.24 | mbedtls3 | before 2.12.0-r0 | 2.12.0-r0 |
| Alpine:v3.8 | mbedtls | before 2.7.5-r0 | 2.7.5-r0 |
| Debian:12 | mbedtls | before 2.12.0-1 | 2.12.0-1 |
| Debian:8 | polarssl | before 1.3.9-2.1+deb8u4 | 1.3.9-2.1+deb8u4 |
| Debian:9 | mbedtls | before 2.4.2-1+deb9u3 | 2.4.2-1+deb9u3 |
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-2018-1000520Jun 26, 2018 · ARM mbedTLS version 2.7.0 and earlier contains a Ciphersuite Allows Incorrectly Signed Certificates vulnerability in…30Monitor
- ← EarlierCVE-2018-0497Jul 28, 2018 · ARM mbed TLS before 2.12.0, before 2.7.5, and before 2.1.14 allows remote attackers to achieve partial plaintext recovery (for a CBC based…24Monitor
- Later →CVE-2018-19608Dec 5, 2018 · Arm Mbed TLS before 2.14.1, before 2.7.8, and before 2.1.17 allows a local unprivileged attacker to recover the plaintext of RSA…18Monitor
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.12.0-r0 · Alpine:v3.10 | Package registry (OSV) |
| alpine:mbedtls2 | 2.12.0-r0 · Alpine:v3.20 | Package registry (OSV) |
| alpine:mbedtls3 | 2.12.0-r0 · Alpine:v3.24 | Package registry (OSV) |
| debian:mbedtls | 2.12.0-1 · Debian:12 | Package registry (OSV) |
| debian:polarssl | 1.3.9-2.1+deb8u4 · Debian:8 | 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
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.