CVE-2017-2784: An exploitable free of a stack pointer vulnerability exists in the x509 certificate parsing code of ARM mbed TLS before 1.3.19, 2.x before…
Noroxi assessment
Priority: Monitor (action score 33/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.3% (FIRST EPSS); higher than 89% 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. Special conditions such as timing or configuration are required.
- Fixed version: mbedtls (Alpine:v3.10) 2.4.2-r0; mbedtls2 (Alpine:v3.20) 2.4.2-r0; mbedtls3 (Alpine:v3.24) 2.4.2-r0.
Low priority for now. Upgrade to mbedtls (Alpine:v3.10) 2.4.2-r0; mbedtls2 (Alpine:v3.20) 2.4.2-r0; mbedtls3 (Alpine:v3.24) 2.4.2-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
An exploitable free of a stack pointer vulnerability exists in the x509 certificate parsing code of ARM mbed TLS before 1.3.19, 2.x before 2.1.7, and 2.4.x before 2.4.2. A specially crafted x509 certificate, when parsed by mbed TLS library, can cause an invalid free of a stack pointer leading to a potential remote code execution. In order to exploit this vulnerability, an attacker can act as either a client or a server on a network to deliver malicious x509 certificates to vulnerable applications.
- Published
- Apr 20, 2017
- Updated
- Jun 16, 2026
- EPSS
- 3.3% · 89th percentile
- CWE
- CWE-295
Report tools
Action score
33
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.3%
CNA vs NVD score
- NVD
- 8.1
- CNA · talos
- 8.1
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
| Vendor | Product | CPE |
|---|---|---|
| trustedfirmware | mbed tls | cpe:2.3:a:trustedfirmware:mbed_tls |
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 (talos). Independent of NVD's CPE analysis and usually ahead of it.
ARM mbed TLS
- 2.4.0affected
Affected versions · NVD (10)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- trustedfirmware mbed tlsup to 1.3.18 inclusive
- trustedfirmware mbed tls2.0.0
- trustedfirmware mbed tls2.1.0
- trustedfirmware mbed tls2.1.1
- trustedfirmware mbed tls2.1.2
- trustedfirmware mbed tls2.1.3
- trustedfirmware mbed tls2.1.4
- trustedfirmware mbed tls2.1.5
- trustedfirmware mbed tls2.1.6
- trustedfirmware mbed tls2.4.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.4.2-r0 | 2.4.2-r0 |
| Alpine:v3.20 | mbedtls2 | before 2.4.2-r0 | 2.4.2-r0 |
| Alpine:v3.24 | mbedtls3 | before 2.4.2-r0 | 2.4.2-r0 |
| Debian:12 | mbedtls | before 2.4.2-1 | 2.4.2-1 |
| 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-5.1 | 1.3.19-5.1 |
Same product
trustedfirmware: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-34875An issue was discovered in Mbed TLS through 3.6.5 and TF-PSA-Crypto 1.0.0.39Monitor
- CVE-2024-49195Mbed TLS 3.5.x through 3.6.x before 3.6.2 has a buffer underrun in pkwrite when writing an opaque key pair39Monitor
- CVE-2024-45159An issue was discovered in Mbed TLS 3.x before 3.6.1.39Monitor
Published before and after this one in the same product
- Later →CVE-2021-45450Dec 21, 2021 · In Mbed TLS before 2.28.0 and 3.x before 3.1.0, psa_cipher_generate_iv and psa_cipher_encrypt allow policy bypass or oracle-based…30Monitor
- Later →CVE-2023-45199Oct 6, 2023 · Mbed TLS 3.2.x through 3.4.x before 3.5 has a Buffer Overflow that can lead to remote Code execution.39Monitor
- Later →CVE-2024-23744Jan 21, 2024 · An issue was discovered in Mbed TLS 3.5.1.30Monitor
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.4.2-r0 · Alpine:v3.10 | Package registry (OSV) |
| alpine:mbedtls2 | 2.4.2-r0 · Alpine:v3.20 | Package registry (OSV) |
| alpine:mbedtls3 | 2.4.2-r0 · Alpine:v3.24 | Package registry (OSV) |
| debian:mbedtls | 2.4.2-1 · Debian:12 | 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-5.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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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.
- Special conditions such as timing or configuration are required.
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
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-295 · Improper Certificate ValidationCVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.
The bug in code
The whole CWE-295 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) {
// Left empty for the test environment
}Fixed
val client = OkHttpClient.Builder()
.certificatePinner(
CertificatePinner.Builder()
.add("api.sirius.example", "sha256/…")
.build()
).build()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)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.