# CVE-2024-3049: Booth: specially crafted hash can lead to invalid hmac being accepted by booth server > Attackers can bypass HMAC validation in Booth cluster ticket manager by submitting specially crafted hashes, compromising authentication integrity. - **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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 Jun 2024 - **Updated:** 17 Mar 2026 - **Also known as:** ALSA-2024:3659, ALSA-2024:3661, AZL-42530, AZL-42540, DEBIAN-CVE-2024-3049, DLA-3894-1, DSA-5777-1, GHSA-gqh6-f673-ccgc, OESA-2024-2048, OESA-2024-2049, OESA-2024-2050, RHSA-2024:3657, RHSA-2024:3658, RHSA-2024:3659, RHSA-2024:3660, RHSA-2024:3661, RHSA-2024:4400, RHSA-2024:4411, RLSA-2024:3659, RLSA-2024:3661, SUSE-SU-2024:2040-1, SUSE-SU-2024:2041-1, SUSE-SU-2024:2042-1, SUSE-SU-2024:2062-1, SUSE-SU-2024:2063-1, SUSE-SU-2024:2251-1, UBUNTU-CVE-2024-3049, USN-8832-1, openSUSE-SU-2024:14045-1 ## What is CVE-2024-3049? CVE-2024-3049 is a medium-severity vulnerability in Redhat Enterprise Linux, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A flaw was found in Booth, a cluster ticket manager. If a specially-crafted hash is passed to gcry_md_get_algo_dlen(), it may allow an invalid HMAC to be accepted by the Booth server. Weakness: CWE-345 (Insufficient Verification of Data Authenticity) ## Which versions are affected by CVE-2024-3049? It affects 8 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `booth` | AlmaLinux:8 | All versions | 1.1-1.el8_10.1 | | `booth-arbitrator` | AlmaLinux:8 | All versions | 1.1-1.el8_10.1 | | `booth-core` | AlmaLinux:8 | All versions | 1.1-1.el8_10.1 | | `booth-site` | AlmaLinux:8 | All versions | 1.1-1.el8_10.1 | | `booth-test` | AlmaLinux:8 | All versions | 1.1-1.el8_10.1 | | `booth` | AlmaLinux:9 | All versions | 1.1-1.el9_4.1 | | `booth-arbitrator` | AlmaLinux:9 | All versions | 1.1-1.el9_4.1 | | `booth-core` | AlmaLinux:9 | All versions | 1.1-1.el9_4.1 | | `booth-site` | AlmaLinux:9 | All versions | 1.1-1.el9_4.1 | | `booth-test` | AlmaLinux:9 | All versions | 1.1-1.el9_4.1 | | `booth` | Red Hat:enterprise_linux:8::highavailability | All versions | 0:1.1-1.el8_10.1 | | `booth-arbitrator` | Red Hat:enterprise_linux:8::highavailability | All versions | 0:1.1-1.el8_10.1 | | `booth-core` | Red Hat:enterprise_linux:8::highavailability | All versions | 0:1.1-1.el8_10.1 | | `booth-core-debuginfo` | Red Hat:enterprise_linux:8::highavailability | All versions | 0:1.1-1.el8_10.1 | | `booth-debugsource` | Red Hat:enterprise_linux:8::highavailability | All versions | 0:1.1-1.el8_10.1 | | `booth-site` | Red Hat:enterprise_linux:8::highavailability | All versions | 0:1.1-1.el8_10.1 | | `booth-test` | Red Hat:enterprise_linux:8::highavailability | All versions | 0:1.1-1.el8_10.1 | | `booth` | Red Hat:enterprise_linux:8::resilientstorage | All versions | 0:1.1-1.el8_10.1 | | `booth-arbitrator` | Red Hat:enterprise_linux:8::resilientstorage | All versions | 0:1.1-1.el8_10.1 | | `booth-core` | Red Hat:enterprise_linux:8::resilientstorage | All versions | 0:1.1-1.el8_10.1 | | `booth-core-debuginfo` | Red Hat:enterprise_linux:8::resilientstorage | All versions | 0:1.1-1.el8_10.1 | | `booth-debugsource` | Red Hat:enterprise_linux:8::resilientstorage | All versions | 0:1.1-1.el8_10.1 | | `booth-site` | Red Hat:enterprise_linux:8::resilientstorage | All versions | 0:1.1-1.el8_10.1 | | `booth-test` | Red Hat:enterprise_linux:8::resilientstorage | All versions | 0:1.1-1.el8_10.1 | | `booth` | Red Hat:enterprise_linux:9::highavailability | All versions | 0:1.1-1.el9_4.1 | | `booth-arbitrator` | Red Hat:enterprise_linux:9::highavailability | All versions | 0:1.1-1.el9_4.1 | | `booth-core` | Red Hat:enterprise_linux:9::highavailability | All versions | 0:1.1-1.el9_4.1 | | `booth-core-debuginfo` | Red Hat:enterprise_linux:9::highavailability | All versions | 0:1.1-1.el9_4.1 | | `booth-debugsource` | Red Hat:enterprise_linux:9::highavailability | All versions | 0:1.1-1.el9_4.1 | | `booth-site` | Red Hat:enterprise_linux:9::highavailability | All versions | 0:1.1-1.el9_4.1 | | `booth-test` | Red Hat:enterprise_linux:9::highavailability | All versions | 0:1.1-1.el9_4.1 | | `booth` | Red Hat:enterprise_linux:9::resilientstorage | All versions | 0:1.1-1.el9_4.1 | | `booth-arbitrator` | Red Hat:enterprise_linux:9::resilientstorage | All versions | 0:1.1-1.el9_4.1 | | `booth-core` | Red Hat:enterprise_linux:9::resilientstorage | All versions | 0:1.1-1.el9_4.1 | | `booth-core-debuginfo` | Red Hat:enterprise_linux:9::resilientstorage | All versions | 0:1.1-1.el9_4.1 | | `booth-debugsource` | Red Hat:enterprise_linux:9::resilientstorage | All versions | 0:1.1-1.el9_4.1 | | `booth-site` | Red Hat:enterprise_linux:9::resilientstorage | All versions | 0:1.1-1.el9_4.1 | | `booth-test` | Red Hat:enterprise_linux:9::resilientstorage | All versions | 0:1.1-1.el9_4.1 | | `booth` | Red Hat:rhel_aus:8.4::highavailability | All versions | 0:1.0-199.1.ac1d34c.git.el8_4.2 | | `booth-arbitrator` | Red Hat:rhel_aus:8.4::highavailability | All versions | 0:1.0-199.1.ac1d34c.git.el8_4.2 | Products: Clusterlabs Booth, Redhat Enterprise Linux, Redhat Enterprise Linux Eus, Redhat Enterprise Linux for Arm 64, Redhat Enterprise Linux for Ibm Z Systems, Redhat Enterprise Linux for Ibm Z Systems Eus, Redhat Enterprise Linux for Power Little Endian Eus, Redhat Enterprise Linux Server Update Services for Sap Solutions. ## How do I fix CVE-2024-3049? Apply the vendor's patch. ## Is CVE-2024-3049 being exploited? There is no known exploitation of CVE-2024-3049 in the wild and no public exploit code. ## Other vulnerabilities in Redhat Enterprise Linux - [CVE-2022-2553](https://insights.sbomify.com/CVE-2022-2553/): Auth bypass in Booth (medium 6.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-3049 and fix it if it is affected. What it is: CVE-2024-3049 is a medium-severity vulnerability in Redhat Enterprise Linux, published on 6 Jun 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-3049 in the wild and no public exploit code. Affected product: Redhat Enterprise Linux. 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-3049/ (Markdown: https://insights.sbomify.com/CVE-2024-3049/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-3049 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-3049 - OSV: https://osv.dev/vulnerability/CVE-2024-3049 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-3049/ Summaries are generated and may contain mistakes; the official description above is the record.