Strix
26.1K

CVE-2016-0270

UnknownEPSS 3.10%

Last modified

CVE-2016-0270 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 3.10% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
3.10%

86.1th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
IbmClient Application Access1.0.0.1
IbmDomino9.0.1.3
IbmDomino9.0.1.4
IbmDomino9.0.1.5
IbmNotes9.0.1.3
IbmNotes9.0.1.4
IbmNotes9.0.1.5

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-0270?
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.
How severe is CVE-2016-0270?
Severity scoring for CVE-2016-0270 is pending analysis. The EPSS model estimates a 3.10% probability of exploitation in the next 30 days.
How do I fix CVE-2016-0270?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2016

View all 2016CVEs →

Are you affected by CVE-2016-0270?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST