Cloudanix VulnDB

CVE-2024-50305

None

CVSS

—

EPSS

0.9%

Published

Nov 14, 2024

CISA due date

—

Cloudanix analysis

Monitor only SSVC: Track

A problem in the web traffic handling software can cause it to stop working when it receives certain normal-looking web requests, interrupting service until it is restarted or updated.

Exploitation
Remote Unauthenticated
Attacker needs
None
Complexity
Low
Impact
Denial Of Service
Component
Network Service
Class
Denial of service
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

A specially crafted but valid Host header triggers a crash in Apache Traffic Server on certain platforms due to improper handling during request processing.

Why it matters to the business

Service availability is disrupted as the proxy or caching layer becomes unresponsive, leading to downtime for dependent applications and potential loss of traffic handling capacity until restart.

How an attack unfolds

An attacker sends an HTTP request containing a valid but maliciously formatted Host header to an affected Apache Traffic Server instance; the server fails to process it correctly and terminates, resulting in a denial of service. No authentication or complex setup is required.

How to fix it

Upgrade Apache Traffic Server to version 9.2.6 or 10.0.2. For the GIT repository, apply the fix from commit de3e58726f6f58a95266a41eaa31ff3c6fc14336. Apply the listed kernel and package updates for affected Ubuntu releases where Traffic Server is deployed.

How to confirm the fix worked

After upgrade, confirm the running version reports 9.2.6 or higher; test with representative Host header requests to verify the process no longer crashes; review release notes for the fix commit.

Typical attack path

  1. Identify an exposed Apache Traffic Server instance running versions 9.2.0-9.2.5
  2. Craft an HTTP request with a valid Host header field designed to trigger the crash condition
  3. Send the request to the server
  4. Observe server process termination and service unavailability

How to detect it

Monitor system and application logs for unexpected Traffic Server process crashes or restarts coinciding with incoming HTTP requests; correlate with proxy access logs showing Host header values around the time of failure.

What your security team should do

  • Prioritize upgrade of all Apache Traffic Server instances to 9.2.6 or 10.0.2 within maintenance windows
  • Inventory deployments to identify any remaining 9.2.0-9.2.5 versions
  • Implement process monitoring and automatic restart for the Traffic Server service as a temporary control
  • Review network exposure and apply access controls to limit untrusted Host header traffic if upgrade is delayed

The record

Valid Host header field can cause Apache Traffic Server to crash on some platforms. This issue affects Apache Traffic Server: from 9.2.0 through 9.2.5. Users are recommended to upgrade to version 9.2.6, which fixes the issue, or 10.0.2, which does not have the issue.

Affected packages

Ecosystem Package Introduced Fixed
Debian:11 trafficserver 0 No fix
Debian:12 trafficserver 0 No fix
Debian:12 trafficserver 0 9.2.5+ds-0+deb12u2
Ubuntu:16.04:LTS trafficserver 0 No fix
Ubuntu:18.04:LTS trafficserver 0 No fix
Ubuntu:20.04:LTS trafficserver 0 No fix
Ubuntu:22.04:LTS trafficserver 0 No fix
Ubuntu:22.04:LTS trafficserver 0 9.1.1+ds-2ubuntu0.1
Ubuntu:24.04:LTS trafficserver 0 No fix
Ubuntu:24.04:LTS trafficserver 0 9.2.3+ds-1+deb12u1ubuntu0.1
Ubuntu:24.10 trafficserver 0 No fix
Ubuntu:25.04 trafficserver 0 No fix
Ubuntu:25.10 trafficserver 0 No fix
Ubuntu:25.10 trafficserver 0 9.2.5+ds-1ubuntu2.1
Ubuntu:Pro:16.04:LTS trafficserver 0 No fix
Ubuntu:Pro:18.04:LTS trafficserver 0 No fix
Ubuntu:Pro:20.04:LTS trafficserver 0 No fix
Ubuntu:Pro:22.04:LTS trafficserver 0 No fix

Related vulnerabilities