CVE-2019-15847
No exploitation reported by the sources we read.
- Published2019-09-02
- Fixed in10.1.0 · 9.3.0 · 8.4.0 · 7.5.0
- WeaknessCWE-331
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « 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
The POWER9 backend in GNU Compiler Collection (GCC) before version 10 could optimize multiple calls of the __builtin_darn intrinsic into a single call, thus reducing the entropy of the random number generator. This occurred because a volatile operation was not specified. For example, within a single execution of a program, the output of every __builtin_darn() call may be the same.
Timeline
dates in UTC- 2019-09-0223:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2019-15847?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2019-15847?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 10.x | ≥ 10.0, < 10.1.0 | 10.1.0 | NVD |
| 9.x | ≥ 9.0, < 9.3.0 | 9.3.0 | NVD |
| 8.x | ≥ 8.0, < 8.4.0 | 8.4.0 | NVD |
| 7.5 | < 7.5.0 | 7.5.0 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 15.0 | = 15.0 | no fix published | NVD |
| 15.1 | = 15.1 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Gnu gcc to 10.1.0 · 9.3.0 · 8.4.0 · 7.5.0
Advisories and patches
- gcc.gnu.orgVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.17.5read 2026-10-23
- NVDCVSS 2.05read 2026-10-23
- NVDweakness (CWE)CWE-331read 2026-10-23
- FIRST EPSSEPSS score3.2 %2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Published
- 2019-09-02
- Last Modified
- 2026-10-14
- NVD status
- Modified
Frequently asked questions
What is CVE-2019-15847?
Is CVE-2019-15847 actively exploited?
What is the CVSS score for CVE-2019-15847?
Hear about the next vulnerability in your software
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 ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.