CVE-2019-12904

In Libgcrypt 1.8.4, the C implementation of AES is vulnerable to a flush-and-reload side-channel attack because physical addresses are available to other processes. (The C implementation is used on platforms where an assembly-language implementation is unavailable.) NOTE: the vendor's position is that the issue report cannot be validated because there is no description of an attack

Published: 2019-06-20 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-12904 is rated Moderate Risk (40.7/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.25%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2019-12904

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-12 0.19% 0.25% +0.06%
2 2025-11-21 0.41% 0.19% -0.22%
3 2025-11-18 — 0.41% —

Full EPSS history (16 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-12904

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.9 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.2 3.6 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2019-12904

OS Trackers for CVE-2019-12904

vendor priority summary link
alpine — CVE-2019-12904: 1 source package rows (libgcrypt); 10 state rows across 10 repos (3.10-main, 3.11-main, 3.12-main, 3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 10, open 0. https://security.alpinelinux.org/vuln/CVE-2019-12904
redhat medium — https://access.redhat.com/security/cve/CVE-2019-12904
ubuntu low CVE-2019-12904 low priority: Ubuntu including 2 source packages (libgcrypt11, libgcrypt20), 24 status rows across 12 suites (bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, trusty, upstream, xenial): DNE 11, not-affected 8, ignored 3, needs-triage 2. https://ubuntu.com/security/CVE-2019-12904

Affected software / configurations for CVE-2019-12904

Vendor Product Version Raw CPE
gnupg libgcrypt 1.8.4 cpe:2.3:a:gnupg:libgcrypt:1.8.4:*:*:*:*:*:*:*
opensuse leap 15.0 cpe:2.3:o:opensuse:leap:15.0:*:*:*:*:*:*:*

References for CVE-2019-12904

cvelogic Threat Intelligence