CVE-2017-17382 json
Citrix NetScaler Application Delivery Controller (ADC) and NetScaler Gateway 10.5 before build 67.13, 11.0 before build 71.22, 11.1 before…
published 8y ago modified 4mo ago also EUVD-2017-8548
- cvss
- 5.9
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 13.9%
- EPSS 13.9% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Metasploit
Summary
Citrix NetScaler Application Delivery Controller (ADC) and NetScaler Gateway 10.5 before build 67.13, 11.0 before build 71.22, 11.1 before build 56.19, and 12.0 before build 53.22 might allow remote attackers to decrypt TLS ciphertext data by leveraging a Bleichenbacher RSA padding oracle, aka a ROBOT attack.
Is CVE-2017-17382 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (Metasploit auxiliary/scanner/ssl/bleichenbacher_oracle)
- Published
Exploit prediction
13.88% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
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 | 5.9 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-327 Use of a Broken or Risky Cryptographic Algorithm
References
-
support.citrix.com
/article/ctx230238
vendor-advisory
-
robotattack.org
/
third-party-advisory
-
securityfocus.com
/bid/102173
vdb-entry, third-party-advisory
-
kb.cert.org
/vuls/id/144389
third-party-advisory, us-government-resource
-
securitytracker.com
/id/1039985
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-17382
- NVD CVE-2017-17382
Fencer Intel 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.