# CVE-2019-12904: Information disclosure in n/a

> A flush-and-reload side-channel vulnerability in Libgcrypt's C AES implementation could allow local attackers to recover cryptographic keys.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jun 2019
- **Updated:** 14 Oct 2026
- **Also known as:** ALPINE-CVE-2019-12904, GHSA-w862-39x5-q88x, SUSE-SU-2019:1859-1, SUSE-SU-2019:1971-1, openSUSE-SU-2019:1792-1

## What is CVE-2019-12904?

CVE-2019-12904 is a medium-severity vulnerability in Opensuse Leap, published on 19 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

## Which versions are affected by CVE-2019-12904?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libgcrypt` | SUSE:Linux Enterprise Module for Basesystem 15 | All versions | 1.8.2-6.17.1 |
| `libgcrypt` | SUSE:Linux Enterprise Module for Basesystem 15 SP1 | All versions | 1.8.2-8.6.2 |
| `libgcrypt` | openSUSE:Leap 15.0 | All versions | 1.8.2-lp150.5.10.1 |

Products: Gnupg Libgcrypt, Opensuse Leap.

## How do I fix CVE-2019-12904?

Apply the vendor's patch.

## Is CVE-2019-12904 being exploited?

There is no known exploitation of CVE-2019-12904 in the wild and no public exploit code.

## Other vulnerabilities in Opensuse Leap

- [CVE-2021-3345](https://insights.sbomify.com/CVE-2021-3345/): Memory corruption in n/a (high 7.8)
- [CVE-2018-6829](https://insights.sbomify.com/CVE-2018-6829/): Weak cryptography in n/a (high 7.5)
- [CVE-2026-41989](https://insights.sbomify.com/CVE-2026-41989/): Memory corruption in Libgcrypt (medium 6.7)
- [CVE-2021-40528](https://insights.sbomify.com/CVE-2021-40528/): Weak cryptography in n/a (medium 5.9)
- [CVE-2017-9526](https://insights.sbomify.com/CVE-2017-9526/): Information disclosure in n/a (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12904 and fix it if it is affected.

What it is: CVE-2019-12904 is a medium-severity vulnerability in Opensuse Leap, published on 19 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-12904 in the wild and no public exploit code.

Affected product: Opensuse Leap. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-12904/ (Markdown: https://insights.sbomify.com/CVE-2019-12904/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-12904
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-12904
- OSV: https://osv.dev/vulnerability/CVE-2019-12904

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-12904/
Summaries are generated and may contain mistakes; the official description above is the record.