Vulnerability in gcc-9 (DEBIAN-CVE-2019-15847)

Summary

Vulnerability in gcc-9 (DEBIAN-CVE-2019-15847). Confidential information can be exposed externally. Mitigation: upgrade to 9.2.1-7 or later.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as DEBIAN-CVE-2019-15847 has been found in gcc-9.
Confidential information can be exposed externally.
What to do: upgrade gcc-9 to 9.2.1-7 or later.
If unsure, ask your IT team or search "gcc-9 DEBIAN-CVE-2019-15847" on the vendor's site.

DEBIAN-CVE-2019-15847 (gcc-9)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 9.2.1-7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in gcc-9.

📍 Affected scope

Check the vendor advisory for the affected versions of gcc-9.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 9.2.1-7.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'gcc-9' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'gcc-9' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で gcc-9 を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade gcc-9 to 9.2.1-7
```
ステージング環境で 9.2.1-7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:11 gcc-9

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.2.1-7"}]}]

References

advisory security-tracker.debian.org