CVE-2024-10295

7.5 HIGH

📋 TL;DR

CVE-2024-10295 is an authentication bypass vulnerability in APICast (Red Hat 3scale API Gateway) where malformed Basic Authentication headers with special characters can bypass authentication checks. This allows unauthorized access to backend APIs protected by the gateway. Organizations using affected versions of Red Hat 3scale API Gateway are impacted.

💻 Affected Systems

Products:
  • Red Hat 3scale API Gateway (APICast)
Versions: APICast versions prior to 3.14.0
Operating Systems: Linux
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects deployments using Basic Authentication. Other authentication methods are not vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of backend APIs, allowing attackers to access sensitive data, modify resources, or perform unauthorized operations as if they were legitimate authenticated users.

🟠

Likely Case

Unauthorized access to protected API endpoints, potentially leading to data exposure, privilege escalation, or service disruption depending on the API's functionality.

🟢

If Mitigated

Limited impact with proper network segmentation, API rate limiting, and additional authentication layers preventing successful exploitation.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires sending specially crafted HTTP requests with malformed Basic Authentication headers containing special characters.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: APICast 3.14.0 and later

Vendor Advisory: https://access.redhat.com/security/cve/CVE-2024-10295

Restart Required: Yes

Instructions:

1. Update to APICast 3.14.0 or later. 2. Restart APICast services. 3. Verify the update was successful.

🔧 Temporary Workarounds

Disable Basic Authentication

all

Switch to alternative authentication methods like OAuth, API keys, or JWT tokens instead of Basic Authentication.

Modify APICast configuration to remove Basic Authentication policies

Input Validation Filter

all

Implement custom policy to validate and sanitize authentication headers before processing.

Create custom APICast policy to validate Authorization headers

🧯 If You Can't Patch

  • Implement Web Application Firewall (WAF) rules to block requests with malformed Basic Authentication headers containing special characters.
  • Add additional authentication layer (API gateway, reverse proxy) in front of APICast to validate requests before they reach the vulnerable component.

🔍 How to Verify

Check if Vulnerable:

Check APICast version. If using Basic Authentication and version is below 3.14.0, the system is vulnerable.

Check Version:

apicast --version

Verify Fix Applied:

After updating to 3.14.0+, test with malformed Basic Authentication headers to confirm authentication is properly enforced.

📡 Detection & Monitoring

Log Indicators:

  • Failed authentication attempts with malformed Authorization headers
  • Successful API access without proper authentication logs

Network Indicators:

  • HTTP requests with Authorization headers containing special characters in Basic auth
  • Unusual API access patterns from unauthenticated sources

SIEM Query:

search 'Authorization: Basic *[^a-zA-Z0-9+/=]*' in HTTP logs

🔗 References

📤 Share & Export