CVE-2017-11671

UnknownEPSS 0.44%

Last modified

CVE-2017-11671 is a vulnerability of currently unknown severity. Under certain circumstances, the ix86_expand_builtin function in i386.c in GNU Compiler Collection (GCC) version 4.6, 4.7, 4.8, 4.9, 5 before 5.5, and 6 before 6.4 will generate instruction sequences that clobber the status flag of the RDRAND and RDSEED intrinsics before it can be read, potentially causing failures of these instructions to go unreported. This could potentially lead to less randomness in random number generation.. EPSS estimates a 0.44% chance of exploitation in the next 30 days.

Description

Under certain circumstances, the ix86_expand_builtin function in i386.c in GNU Compiler Collection (GCC) version 4.6, 4.7, 4.8, 4.9, 5 before 5.5, and 6 before 6.4 will generate instruction sequences that clobber the status flag of the RDRAND and RDSEED intrinsics before it can be read, potentially causing failures of these instructions to go unreported. This could potentially lead to less randomness in random number generation.

Metrics

EPSS Probability
0.44%

35.2th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
GnuGcc4.6
GnuGcc4.7
GnuGcc4.8
GnuGcc4.9
GnuGcc5.0
GnuGcc5.1
GnuGcc5.2
GnuGcc5.3
GnuGcc5.4
GnuGcc6.0
GnuGcc6.1
GnuGcc6.2
GnuGcc6.3

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-11671?
Under certain circumstances, the ix86_expand_builtin function in i386.c in GNU Compiler Collection (GCC) version 4.6, 4.7, 4.8, 4.9, 5 before 5.5, and 6 before 6.4 will generate instruction sequences that clobber the status flag of the RDRAND and RDSEED intrinsics before it can be read, potentially causing failures of these instructions to go unreported. This could potentially lead to less randomness in random number generation.
How severe is CVE-2017-11671?
Severity scoring for CVE-2017-11671 is pending analysis. The EPSS model estimates a 0.44% probability of exploitation in the next 30 days.
How do I fix CVE-2017-11671?
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.

Are you affected by CVE-2017-11671?

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

Scan your code now

Source: NVD / NIST