CVE-2017-13099: wolfSSL Bleichenbacher/ROBOT
Noroxi assessment
Priority: This week (action score 60/100)
- A ready-made attack module is public (Metasploit); exploiting it takes no special expertise.
- A ready-made attack tool exists and the flaw can be exploited over the network without an account, so priority is at least “This week”.
- Probability of exploitation in the next 30 days: 27.3% (FIRST EPSS); higher than 98% 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: wolfssl (Debian:12) 3.13.0+dfsg-1.
Don’t wait for the next maintenance window. Upgrade to wolfssl (Debian:12) 3.13.0+dfsg-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
wolfSSL prior to version 3.12.2 provides a weak Bleichenbacher oracle when any TLS cipher suite using RSA key exchange is negotiated. An attacker can recover the private key from a vulnerable wolfSSL application. This vulnerability is referred to as "ROBOT."
- Published
- Dec 12, 2017
- Updated
- Jun 16, 2026
- EPSS
- 27.3% · 98th percentile
- CWE
- CWE-203
Report tools
Action score
60
Don’t wait for the next maintenance window.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 8 / 30 · 27.3%
- Ready-made attack tool
- 29 / 60 · floor: at least 60
CNA vs NVD score
- NVD
- 5.9
- CNA · certcc
- 7.5
- 1.6 point gap
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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
- Weaponized exploit exists
- 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 |
|---|---|---|
| wolfssl | wolfssl | cpe:2.3:a:wolfssl:wolfssl |
| siemens | scalance w1750d firmware | cpe:2.3:o:siemens:scalance_w1750d_firmware |
| siemens | scalance w1750d | cpe:2.3:h:siemens:scalance_w1750d |
| arubanetworks | instant | cpe:2.3:a:arubanetworks:instant |
Check your server's TLS configuration
The wolfSSL 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 (certcc). Independent of NVD's CPE analysis and usually ahead of it.
wolfSSL wolfSSL
- <3.12.2affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- arubanetworks instantbefore 6.5.4.6
- siemens scalance w1750d firmwarebefore 8.3.0.1
- wolfssl wolfsslbefore 3.12.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | wolfssl | before 3.13.0+dfsg-1 | 3.13.0+dfsg-1 |
Same product
wolfssl: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-11873wolfSSL 4.0.0 has a Buffer Overflow in DoPreSharedKeys in tls13.c when a current identity size is greater than a client identity size.42Plan
- CVE-2017-2800A specially crafted x509 certificate can cause a single out of bounds byte overwrite in wolfSSL through 3.10.2 resulting in potential…42Plan
- CVE-2024-5991Buffer overread in domain name matching40Plan
Published before and after this one in the same product
- ← EarlierCVE-2017-8855May 9, 2017 · wolfSSL before 3.11.0 does not prevent wc_DhAgree from accepting a malformed DH key.30Monitor
- ← EarlierCVE-2014-2903Oct 6, 2017 · CyaSSL does not check the key usage extension in leaf certificates, which allows remote attackers to spoof servers via a crafted server…23Monitor
- Later →CVE-2018-12436Jun 14, 2018 · wolfcrypt/src/ecc.c in wolfSSL before 3.15.1.patch allows a memory-cache side-channel attack on ECDSA signatures, aka the Return Of the…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 |
|---|---|---|
| debian:wolfssl | 3.13.0+dfsg-1 · Debian:12 | Package registry (OSV) |
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Metasploit module ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Metasploit module | auxiliary/scanner/ssl/bleichenbacher_oracleScanner for Bleichenbacher Oracle in RSA PKCS #1 v1.5auxiliary | 2009-06-17 |
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.
- Metasploit-3101 d
- Published
- TodayNov 16, 2026+3260 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: 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
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-203 · Observable DiscrepancyCVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/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.
Attack patterns (CAPEC)
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.