CVE-2024-12534

7.5 HIGH

📋 TL;DR

This vulnerability in open-webui/open-webui allows unauthenticated attackers to submit extremely large payloads in email and password fields during sign-in, causing resource exhaustion and Denial of Service. Any system running the vulnerable version is affected, potentially rendering the web UI unavailable to legitimate users.

💻 Affected Systems

Products:
  • open-webui/open-webui
Versions: v0.3.32
Operating Systems: All platforms running the vulnerable software
Default Config Vulnerable: ⚠️ Yes
Notes: All deployments using the default configuration are vulnerable. The vulnerability affects the sign-in endpoint specifically.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete service outage with server resource exhaustion (CPU, memory, disk space) leading to extended downtime and potential data corruption.

🟠

Likely Case

Temporary service unavailability during attack, degraded performance for legitimate users, and potential system instability.

🟢

If Mitigated

Minimal impact with proper input validation and resource limits in place.

🌐 Internet-Facing: HIGH - The vulnerability is exploitable without authentication and affects the sign-in endpoint which is typically internet-facing.
🏢 Internal Only: MEDIUM - While less exposed, internal attackers could still exploit this to disrupt services.

🎯 Exploit Status

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

Exploitation is straightforward - simply sending large payloads to the sign-in endpoint. No special tools or techniques required.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: v0.3.33 or later

Vendor Advisory: https://huntr.com/bounties/c7c0a4e6-acd3-49b4-8684-2c2c27014b76

Restart Required: No

Instructions:

1. Update open-webui to version v0.3.33 or later. 2. Verify the update was successful. 3. No restart required as this is a web application fix.

🔧 Temporary Workarounds

Implement Web Application Firewall (WAF) rules

all

Configure WAF to block or limit large payloads to the sign-in endpoint

Rate limiting on sign-in endpoint

all

Implement request rate limiting to prevent rapid exploitation attempts

🧯 If You Can't Patch

  • Implement reverse proxy with request size limits and input validation
  • Monitor server resources closely and set up alerts for unusual resource consumption

🔍 How to Verify

Check if Vulnerable:

Check if running open-webui version v0.3.32. Attempt to send large payloads (>10MB) to the sign-in endpoint and monitor resource usage.

Check Version:

Check package.json or application configuration for version information, or use: docker inspect open-webui | grep version

Verify Fix Applied:

After updating, attempt to send large payloads to sign-in endpoint - requests should be rejected or truncated. Verify version is v0.3.33 or later.

📡 Detection & Monitoring

Log Indicators:

  • Unusually large request sizes to /api/auth/signin endpoint
  • Multiple failed login attempts with large payloads
  • High resource usage alerts (CPU, memory, disk)

Network Indicators:

  • Large HTTP POST requests to sign-in endpoint
  • Multiple connection attempts from single IP to sign-in

SIEM Query:

source="web_server" AND (uri_path="/api/auth/signin" AND request_size>10000000) OR (error_message="request entity too large")

🔗 References

📤 Share & Export