CVE-2024-3049

5.9 MEDIUM

📋 TL;DR

This vulnerability in Booth cluster ticket manager allows an attacker to bypass HMAC validation by providing a specially-crafted hash to gcry_md_get_algo_dlen(). This could enable unauthorized access or ticket manipulation in Booth server deployments. Systems running vulnerable versions of Booth are affected.

💻 Affected Systems

Products:
  • Booth cluster ticket manager
Versions: Specific versions not provided in references; check Red Hat advisories for exact affected versions
Operating Systems: Linux distributions with Booth packages, particularly Red Hat Enterprise Linux
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects systems where Booth server is running and configured to use HMAC validation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

An attacker could bypass authentication and gain unauthorized access to cluster management functions, potentially disrupting cluster operations or manipulating ticket assignments.

🟠

Likely Case

Unauthorized ticket validation leading to improper cluster node participation or resource allocation issues.

🟢

If Mitigated

With proper network segmentation and access controls, impact would be limited to the Booth service itself without broader cluster compromise.

🌐 Internet-Facing: MEDIUM - Booth servers exposed to internet could be targeted, but exploitation requires specific knowledge of Booth protocol.
🏢 Internal Only: MEDIUM - Internal attackers with network access to Booth ports could exploit this vulnerability.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

Exploitation requires understanding of Booth protocol and ability to craft specific hash values to trigger the gcry_md_get_algo_dlen() flaw.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check specific Red Hat advisories for patched versions

Vendor Advisory: https://access.redhat.com/errata/RHSA-2024:3657

Restart Required: Yes

Instructions:

1. Identify affected Booth packages. 2. Apply updates via yum update booth* or dnf update booth*. 3. Restart Booth services. 4. Verify patch application.

🔧 Temporary Workarounds

Network Access Restriction

linux

Restrict network access to Booth server ports (default 9929/tcp) to only trusted cluster nodes.

iptables -A INPUT -p tcp --dport 9929 -s trusted_node_ip -j ACCEPT
iptables -A INPUT -p tcp --dport 9929 -j DROP

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate Booth servers from untrusted networks
  • Monitor Booth server logs for unusual authentication attempts or hash validation failures

🔍 How to Verify

Check if Vulnerable:

Check Booth package version: rpm -q booth or dpkg -l | grep booth

Check Version:

rpm -q booth --queryformat '%{VERSION}-%{RELEASE}\n'

Verify Fix Applied:

Verify updated package version and restart Booth service: systemctl restart boothd

📡 Detection & Monitoring

Log Indicators:

  • Unusual HMAC validation failures in Booth logs
  • Multiple authentication attempts from single source
  • Invalid hash length errors

Network Indicators:

  • Unusual traffic patterns to Booth port 9929
  • Multiple connection attempts with varying hash payloads

SIEM Query:

source="booth.log" AND ("HMAC" OR "validation" OR "gcry_md") AND ("fail" OR "error" OR "invalid")

🔗 References

📤 Share & Export