CVE-2016-0270 json
IBM Domino 9.0.1 Fix Pack 3 Interim Fix 2 through 9.0.1 Fix Pack 5 Interim Fix 1, when using TLS and AES GCM, uses random nonce generation,…
published 2017-02-08 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-0305
- cvss
- 5.9
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.1%
- EPSS 3.1% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
IBM Domino 9.0.1 Fix Pack 3 Interim Fix 2 through 9.0.1 Fix Pack 5 Interim Fix 1, when using TLS and AES GCM, uses random nonce generation, which makes it easier for remote attackers to obtain the authentication key and spoof data by leveraging the reuse of a nonce in a session and a "forbidden attack." NOTE: this CVE has been incorrectly used for GCM nonce reuse issues in other products; see CVE-2016-10213 for the A10 issue, CVE-2016-10212 for the Radware issue, and CVE-2017-5933 for the Citrix issue.
Patch / fix
Exploit prediction
3.10% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
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-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
www-01.ibm.com
/support/docview.wss?uid=swg21979604
mitigation, patch, vendor-advisory
-
www-01.ibm.com
/support/docview.wss?uid=swg21979673
mitigation, patch, vendor-advisory
-
www-01.ibm.com
/support/docview.wss?uid=swg21979669
mitigation, patch, vendor-advisory
-
securityfocus.com
/bid/96062
vdb-entry, third-party-advisory
-
github.com
/nonce-disrespect/nonce-disrespect
third-party-advisory
- support.citrix.com /article/CTX220329
-
securitytracker.com
/id/1037795
vdb-entry
Sources
- CVE List CVE-2016-0270
- NVD CVE-2016-0270
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.