Skip to main content
No exploitation reportedFix available

CVE-2017-11671

No exploitation reported by the sources we read.

  • Published2017-07-26
  • WeaknessCWE-338

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2017-07-2621:29CVE publishedNVD

Versions per branch

NVD
Gnu gcc
BranchAffectedFixed in
4.6= 4.6no fix published
4.7= 4.7no fix published
4.8= 4.8no fix published
4.9= 4.9no fix published
5.0= 5.0no fix published
5.1= 5.1no fix published
5.2= 5.2no fix published
5.3= 5.3no fix published
5.4= 5.4no fix published
6.0= 6.0no fix published
6.1= 6.1no fix published
6.2= 6.2no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • fixincludesTuxCare:Ubuntu:16.04all versions · fixed in 1:5.4.0-6ubuntu1~16.04.12+tuxcare.els1
  • gccRed Hat:enterprise_linux:7::workstationall versions · fixed in 0:4.8.5-28.el7and 40 other packages
  • gccRed Hat:enterprise_linux:7::serverall versions · fixed in 0:4.8.5-28.el7and 40 other packages
  • gccRed Hat:enterprise_linux:7::computenodeall versions · fixed in 0:4.8.5-28.el7and 40 other packages
  • gccRed Hat:enterprise_linux:7::clientall versions · fixed in 0:4.8.5-28.el7and 40 other packages
  • gcc-3.3Ubuntu:24.04:LTSall versions · no fixed version listedand 4 other packages
  • gcc-3.3Ubuntu:22.04:LTSall versions · no fixed version listedand 6 other packages
  • gcc-3.3Ubuntu:20.04:LTSall versions · no fixed version listedand 6 other packages

25 more package ranges on OSV.dev

Vendor advisories

  • RHSA-2018:0849 Red Hat Product Security579 products fixed

    Red Hat Security Advisory: gcc security, bug fix, and enhancement update

Full record on NVD

Fix

  1. Vendor fix Red Hat Product Security RHSA-2018:0849 · 579 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Published
2017-07-26
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-9qgp-g97v-qq69

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.

Is CVE-2017-11671 actively exploited?

Active exploitation of CVE-2017-11671 has not been confirmed. Its EPSS score was 0.5% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2017-11671?

CVE-2017-11671 has a CVSS v3 base score of 4 (MEDIUM severity), with vector string CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N.

Running gcc security, bug fix,? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record