CVE-2014-8627: PolarSSL 1.3.8 does not properly negotiate the signature algorithm to use, which allows remote attackers to conduct downgrade attacks via…
Noroxi assessment
Priority: Monitor (action score 21/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: 2% (FIRST EPSS); higher than 81.9% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: mbedtls (openSUSE:Tumbleweed) 2.4.0-1.2; mbedtls-2 (openSUSE:Tumbleweed) 2.28.3-1.1; mbedtls-3 (openSUSE:Tumbleweed) 3.6.6-1.1.
Low priority for now. Upgrade to mbedtls (openSUSE:Tumbleweed) 2.4.0-1.2; mbedtls-2 (openSUSE:Tumbleweed) 2.28.3-1.1; mbedtls-3 (openSUSE:Tumbleweed) 3.6.6-1.1 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
PolarSSL 1.3.8 does not properly negotiate the signature algorithm to use, which allows remote attackers to conduct downgrade attacks via unspecified vectors.
- Published
- Nov 24, 2014
- Updated
- Jun 16, 2026
- EPSS
- 2.0% · 81th percentile
- CWE
- CWE-310
Report tools
Action score
21
Low priority for now.
- CVSS
- 20 / 40 · 5.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.0%
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.
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 |
|---|---|---|
| polarssl | polarssl | cpe:2.3:a:polarssl:polarssl |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- polarssl polarssl1.3.8
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| openSUSE:Tumbleweed | mbedtls | before 2.4.0-1.2 | 2.4.0-1.2 |
| openSUSE:Tumbleweed | mbedtls-2 | before 2.28.3-1.1 | 2.28.3-1.1 |
| openSUSE:Tumbleweed | mbedtls-3 | before 3.6.6-1.1 | 3.6.6-1.1 |
Same product
polarssl: all recordsOther highest-scoring records for the same primary product.
- CVE-2011-4574PolarSSL versions prior to v1.1 use the HAVEGE random number generation algorithm.39Monitor
- CVE-2014-9744Memory leak in PolarSSL before 1.3.9 allows remote attackers to cause a denial of service (memory consumption) via a large number of…32Monitor
- CVE-2014-8628Memory leak in PolarSSL before 1.2.12 and 1.3.x before 1.3.9 allows remote attackers to cause a denial of service (memory consumption) via…32Monitor
Published before and after this one in the same product
- ← EarlierCVE-2013-5914Oct 26, 2013 · Buffer overflow in the ssl_read_record function in ssl_tls.c in PolarSSL before 1.1.8, when using TLS 1.1, might allow remote attackers to…28Monitor
- ← EarlierCVE-2014-4911Jul 22, 2014 · The ssl_decrypt_buf function in library/ssl_tls.c in PolarSSL before 1.2.11 and 1.3.x before 1.3.8 allows remote attackers to cause a…21Monitor
- Later →CVE-2015-1182Jan 27, 2015 · The asn1_get_sequence_of function in library/asn1parse.c in PolarSSL 1.0 through 1.2.12 and 1.3.x through 1.3.9 does not properly…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 |
|---|---|---|
| opensuse:mbedtls | 2.4.0-1.2 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:mbedtls-2 | 2.28.3-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:mbedtls-3 | 3.6.6-1.1 · openSUSE:Tumbleweed | 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
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- P · data or configuration can be modified
- Availability
- none
- Attack complexity
- Low
- Confidentiality impact
- None
- Integrity impact
- P
- Availability impact
- None
Weakness class (CWE)
CWE-310 · Cryptographic IssuesCVSS vector
AV:N/AC:L/Au:N/C:N/I:P/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 (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.