CVE-2017-6168 in the critical feed json
On BIG-IP versions 11.6.0-11.6.2 (fixed in 11.6.2 HF1), 12.0.0-12.1.2 HF1 (fixed in 12.1.2 HF2), or 13.0.0-13.0.0 HF2 (fixed in 13.0.0 HF3)…
published 2017-11-17 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-15233
- cvss
- 7.4
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 19.6%
- EPSS 19.6% chance of exploitation in 30 days, percentile 97%
- public exploits
- 1
- Metasploit
Summary
On BIG-IP versions 11.6.0-11.6.2 (fixed in 11.6.2 HF1), 12.0.0-12.1.2 HF1 (fixed in 12.1.2 HF2), or 13.0.0-13.0.0 HF2 (fixed in 13.0.0 HF3) a virtual server configured with a Client SSL profile may be vulnerable to an Adaptive Chosen Ciphertext attack (AKA Bleichenbacher attack) against RSA, which when exploited, may result in plaintext recovery of encrypted messages and/or a Man-in-the-middle (MiTM) attack, despite the attacker not having gained access to the server's private key itself, aka a ROBOT attack.
Timeline
- First public exploit (Metasploit auxiliary/scanner/ssl/bleichenbacher_oracle)
- Published
Exploit prediction
19.64% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit auxiliary/scanner/ssl/bleichenbacher_oracle Scanner for Bleichenbacher Oracle in RSA PKCS #1 v1.5 metasploit auxiliary, normal rank, 2009-06-17
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.4 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-203 Observable Discrepancy
References
-
support.f5.com
/csp/article/K21905460
issue-tracking, mitigation, vendor-advisory
-
robotattack.org
/
technical-description, third-party-advisory
-
securityfocus.com
/bid/101901
vdb-entry, third-party-advisory
-
kb.cert.org
/vuls/id/144389
third-party-advisory, us-government-resource
-
securitytracker.com
/id/1039839
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-6168
- NVD CVE-2017-6168
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.