# CVE-2024-28834: Gnutls: vulnerable to minerva side-channel information leak > Attackers can exploit timing side-channels in GnuTLS to leak cryptographic information when specific reproducible key flags are enabled. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 21 Mar 2024 - **Updated:** 22 Oct 2026 - **Also known as:** ALPINE-CVE-2024-28834, ALSA-2024:1784, AZL-37084, AZL-37109, BELL-CVE-2024-28834, CLSA-2024-1726769216, CLSA-2024-1728056228, CLSA-2024-1728056381, DEBIAN-CVE-2024-28834, GHSA-frvc-6356-58xm, OESA-2024-1439, RHSA-2024:1784, RHSA-2024:1997, RHSA-2024:2044, RLSA-2024:1784, UBUNTU-CVE-2024-28834 ## What is CVE-2024-28834? CVE-2024-28834 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 21 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description A flaw was found in GnuTLS. The Minerva attack is a cryptographic vulnerability that exploits deterministic behavior in systems like GnuTLS, leading to side-channel leaks. In specific scenarios, such as when using the GNUTLS_PRIVKEY_FLAG_REPRODUCIBLE flag, it can result in a noticeable step in nonce size from 513 to 512 bits, exposing a potential timing side-channel. Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) ## Which versions are affected by CVE-2024-28834? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `gnutls` | AlmaLinux:8 | All versions | 3.6.16-8.el8_9.3 | | `gnutls-c++` | AlmaLinux:8 | All versions | 3.6.16-8.el8_9.3 | | `gnutls-dane` | AlmaLinux:8 | All versions | 3.6.16-8.el8_9.3 | | `gnutls-devel` | AlmaLinux:8 | All versions | 3.6.16-8.el8_9.3 | | `gnutls-utils` | AlmaLinux:8 | All versions | 3.6.16-8.el8_9.3 | | `gnutls-c++` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.6.16-8.el8_9.3 | | `gnutls-c++-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.6.16-8.el8_9.3 | | `gnutls-dane` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.6.16-8.el8_9.3 | | `gnutls-dane-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.6.16-8.el8_9.3 | | `gnutls-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.6.16-8.el8_9.3 | | `gnutls-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.6.16-8.el8_9.3 | | `gnutls-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.6.16-8.el8_9.3 | | `gnutls-utils` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.6.16-8.el8_9.3 | | `gnutls-utils-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.6.16-8.el8_9.3 | | `gnutls` | Red Hat:enterprise_linux:8::baseos | All versions | 0:3.6.16-8.el8_9.3 | | `gnutls-c++-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:3.6.16-8.el8_9.3 | | `gnutls-dane-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:3.6.16-8.el8_9.3 | | `gnutls-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:3.6.16-8.el8_9.3 | | `gnutls-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:3.6.16-8.el8_9.3 | | `gnutls-utils-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:3.6.16-8.el8_9.3 | | `gnutls-c++` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:3.6.16-5.el8_6.4 | | `gnutls-c++-debuginfo` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:3.6.16-5.el8_6.4 | | `gnutls-dane` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:3.6.16-5.el8_6.4 | | `gnutls-dane-debuginfo` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:3.6.16-5.el8_6.4 | | `gnutls-debuginfo` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:3.6.16-5.el8_6.4 | | `gnutls-debugsource` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:3.6.16-5.el8_6.4 | | `gnutls-devel` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:3.6.16-5.el8_6.4 | | `gnutls-utils` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:3.6.16-5.el8_6.4 | | `gnutls-utils-debuginfo` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:3.6.16-5.el8_6.4 | | `gnutls` | Red Hat:rhel_eus:8.6::baseos | All versions | 0:3.6.16-5.el8_6.4 | | `gnutls-c++-debuginfo` | Red Hat:rhel_eus:8.6::baseos | All versions | 0:3.6.16-5.el8_6.4 | | `gnutls-dane-debuginfo` | Red Hat:rhel_eus:8.6::baseos | All versions | 0:3.6.16-5.el8_6.4 | | `gnutls-debuginfo` | Red Hat:rhel_eus:8.6::baseos | All versions | 0:3.6.16-5.el8_6.4 | | `gnutls-debugsource` | Red Hat:rhel_eus:8.6::baseos | All versions | 0:3.6.16-5.el8_6.4 | | `gnutls-utils-debuginfo` | Red Hat:rhel_eus:8.6::baseos | All versions | 0:3.6.16-5.el8_6.4 | | `gnutls-c++` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:3.6.16-7.el8_8.3 | | `gnutls-c++-debuginfo` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:3.6.16-7.el8_8.3 | | `gnutls-dane` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:3.6.16-7.el8_8.3 | | `gnutls-dane-debuginfo` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:3.6.16-7.el8_8.3 | | `gnutls-debuginfo` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:3.6.16-7.el8_8.3 | ## How do I fix CVE-2024-28834? Apply the vendor's patch. ## Is CVE-2024-28834 being exploited? There is no known exploitation of CVE-2024-28834 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-28834 and fix it if it is affected. What it is: CVE-2024-28834 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 21 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-28834 in the wild and no public exploit code. Affected product: Red Hat Enterprise Linux 10. 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-2024-28834/ (Markdown: https://insights.sbomify.com/CVE-2024-28834/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-28834 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-28834 - OSV: https://osv.dev/vulnerability/CVE-2024-28834 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-28834/ Summaries are generated and may contain mistakes; the official description above is the record.