dbcve.org
Enterprise LinuxOperating system · Redhat

CVE-2024-3049

MEDIUM · 5.9 CVSS v3.1 Published 2024-06-06
Fix available
A fix is available. Upgrade to 1.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise LinuxOperating system
Affected:= 7.0= 8.0= 9.0
Enterprise Linux EusOperating system
Affected:= 8.4= 8.8= 9.2
Enterprise Linux For Arm 64Operating system
Affected:= 8.0_aarch64= 8.8_aarch64= 9.2_aarch64= 9.4_aarch64
Enterprise Linux For Ibm Z SystemsOperating system
Affected:= 8.0_s390x= 9.2_s390x= 9.4_s390x
Enterprise Linux For Ibm Z Systems EusOperating system
Affected:= 8.8_s390x
Enterprise Linux For Power Little Endian EusOperating system
Affected:= 8.0_ppc64le= 8.4_ppc64le= 8.8_ppc64le= 9.2_ppc64le= 9.4_ppc64le
Enterprise Linux Server Update Services For Sap SolutionsOperating system
Affected:= 8.4
BoothApplication
Affected:< 1.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.1 or later
Fixed in 1.1
Vendor patch github.com →
Recommended fix High confidence

Booth >= 1.1

  1. 1. Identify the Booth package version currently installed on the system using: `rpm -q booth` or `dnf list installed booth`
  2. 2. Update the Booth package to version 1.1 or later by running: `dnf update booth` or `yum update booth`
  3. 3. Verify the new version installed correctly: `rpm -q booth` should show version 1.1 or higher
  4. 4. Restart the Booth service if needed to apply the changes: `systemctl restart booth` or as appropriate for your cluster configuration
  5. 5. Verify the service is running properly: `systemctl status booth`

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-3049 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-3049 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data