# CVE-2024-2236: Libgcrypt: vulnerable to marvin attack > A timing side-channel in Libgcrypt's RSA implementation allows remote attackers to decrypt ciphertexts via a Bleichenbacher-style attack. - **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:** 6 Mar 2024 - **Updated:** 15 Oct 2026 - **Also known as:** ALSA-2024:9404, AZL-108024, BELL-CVE-2024-2236, CLSA-2025-1736859209, CLSA-2025-1737656427, CLSA-2025-1744301726, CLSA-2025-1751538844, DEBIAN-CVE-2024-2236, ECHO-6c46-a151-cc7a, GHSA-w2gx-4fh8-wm9f, MGASA-2026-0464, RHSA-2024:9404, RHSA-2025:3530, RHSA-2025:3534, RLSA-2024:9404, ROOT-OS-DEBIAN-12-CVE-2024-2236, SUSE-FU-2026:21213-1, SUSE-FU-2026:21232-1, SUSE-SU-2025:02447-1, SUSE-SU-2025:02464-1, SUSE-SU-2025:02464-2, SUSE-SU-2025:02719-1, SUSE-SU-2025:02752-1, SUSE-SU-2025:02756-1, SUSE-SU-2025:02773-1, SUSE-SU-2025:20490-1, SUSE-SU-2025:20538-1, UBUNTU-CVE-2024-2236, USN-8711-1, openSUSE-FU-2026:20562-1, openSUSE-SU-2025:15239-1 ## What is CVE-2024-2236? CVE-2024-2236 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 6 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts. Weakness: CWE-385 (Covert Timing Channel) ## Which versions are affected by CVE-2024-2236? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libgcrypt` | AlmaLinux:9 | All versions | 1.10.0-11.el9 | | `libgcrypt-devel` | AlmaLinux:9 | All versions | 1.10.0-11.el9 | | `libgcrypt-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.10.0-11.el9 | | `libgcrypt-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.10.0-11.el9 | | `libgcrypt-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.10.0-11.el9 | | `libgcrypt-devel-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.10.0-11.el9 | | `libgcrypt` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.10.0-11.el9 | | `libgcrypt-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.10.0-11.el9 | | `libgcrypt-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.10.0-11.el9 | | `libgcrypt-devel-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.10.0-11.el9 | | `libgcrypt-debuginfo` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:1.10.0-10.el9_2.1 | | `libgcrypt-debugsource` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:1.10.0-10.el9_2.1 | | `libgcrypt-devel` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:1.10.0-10.el9_2.1 | | `libgcrypt-devel-debuginfo` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:1.10.0-10.el9_2.1 | | `libgcrypt` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:1.10.0-10.el9_2.1 | | `libgcrypt-debuginfo` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:1.10.0-10.el9_2.1 | | `libgcrypt-debugsource` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:1.10.0-10.el9_2.1 | | `libgcrypt-devel-debuginfo` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:1.10.0-10.el9_2.1 | | `libgcrypt-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:1.10.0-10.el9_4.1 | | `libgcrypt-debugsource` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:1.10.0-10.el9_4.1 | | `libgcrypt-devel` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:1.10.0-10.el9_4.1 | | `libgcrypt-devel-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:1.10.0-10.el9_4.1 | | `libgcrypt` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1.10.0-10.el9_4.1 | | `libgcrypt-debuginfo` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1.10.0-10.el9_4.1 | | `libgcrypt-debugsource` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1.10.0-10.el9_4.1 | | `libgcrypt-devel-debuginfo` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1.10.0-10.el9_4.1 | | `libgcrypt` | Rocky Linux:9 | All versions | 0:1.10.0-11.el9 | | `libgcrypt` | SUSE:Enterprise Storage 7.1 | All versions | 1.8.2-150100.8.45.1 | | `libgcrypt` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 1.8.2-150100.8.45.1 | | `libgcrypt` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 1.9.4-150400.6.11.1 | | `libgcrypt` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 1.9.4-150400.6.11.1 | | `libgcrypt` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 1.9.4-150500.12.3.3 | | `libgcrypt` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 1.9.4-150500.12.3.3 | | `libgcrypt` | SUSE:Linux Enterprise Micro 5.1 | All versions | 1.8.2-150100.8.45.1 | | `libgcrypt` | SUSE:Linux Enterprise Micro 5.2 | All versions | 1.8.2-150100.8.45.1 | | `libgcrypt` | SUSE:Linux Enterprise Micro 5.3 | All versions | 1.9.4-150400.6.11.1 | | `libgcrypt` | SUSE:Linux Enterprise Micro 5.4 | All versions | 1.9.4-150400.6.11.1 | | `libgcrypt` | SUSE:Linux Enterprise Micro 5.5 | All versions | 1.9.4-150500.12.3.3 | | `libgcrypt` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 1.10.3-150600.3.9.1 | | `libgcrypt` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 1.11.0-150700.5.7.1 | ## How do I fix CVE-2024-2236? Apply the vendor's patch. ## Is CVE-2024-2236 being exploited? There is no known exploitation of CVE-2024-2236 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-2236 and fix it if it is affected. What it is: CVE-2024-2236 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 6 Mar 2024. 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-2024-2236 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-2236/ (Markdown: https://insights.sbomify.com/CVE-2024-2236/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-2236 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-2236 - OSV: https://osv.dev/vulnerability/CVE-2024-2236 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-2236/ Summaries are generated and may contain mistakes; the official description above is the record.