dbcve.org
Traffic ServerApplication · Apache

CVE-2024-50305

HIGH · 7.5 CVSS v3.1 Published 2024-11-14
Fix available
A fix is available. Upgrade to 9.2.6 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
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.

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 · high confidence

A valid but specially crafted Host header field triggers a crash in Apache Traffic Server versions 9.2.0-9.2.5 on certain platforms, leading to denial of service. The vulnerability stems from improper handling of the Host header input, causing an assertion failure or null pointer dereference.

MitigationUpgrade Apache Traffic Server to version 9.2.6 or 10.0.2 which contain the fix. Plan for a maintenance window to perform the upgrade and validate service functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Traffic ServerApplication
Affected:>= 9.0.0, < 9.2.6

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Apache Traffic Server version
    Run 'traffic_server -V' or check the package manager for the installed version of Apache Traffic Server
    Affected if The version is 9.0.0 through 9.2.5 inclusive (versions below 9.2.6 or 10.0.2)
  2. Confirm HTTP processing is enabled
    Check configuration files (typically ats.config or records.conf) for proxy.http.enabled or similar HTTP processing settings
    Affected if HTTP processing is enabled and the server is configured to handle Host headers from incoming requests
  3. Verify the server is exposed to HTTP traffic
    Review network configuration to confirm the Traffic Server is directly accessible on HTTP/HTTPS ports (80/443)
    Affected if The server accepts HTTP connections from clients that could send the crafted Host header
  4. Check platform compatibility
    Review the platform where Apache Traffic Server is deployed (OS version, architecture)
    Affected if Running on a platform affected by this specific vulnerability (certain platforms as noted in CVE description)
  5. Review access logs for crashes
    Examine traffic_server error logs for assertion failures or null pointer dereference errors around the time of requests
    Affected if Recent crash logs show failures related to Host header processing

You are affected if Apache Traffic Server version 9.0.0-9.2.5 is installed, HTTP processing is enabled, and the server handles incoming HTTP requests on affected platforms.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 9.2.6 or later
Fixed in 9.2.6
Interim mitigation

Upgrade Apache Traffic Server to version 9.2.6 or 10.0.2 which contain the fix. Plan for a maintenance window to perform the upgrade and validate service functionality.

Recommended fix High confidence

9.2.6 or 10.0.2

  1. 1. Backup the current Apache Traffic Server configuration and data directories
  2. 2. Stop the Apache Traffic Server service
  3. 3. Download Apache Traffic Server version 9.2.6 or 10.0.2 from the official Apache download repository
  4. 4. Install the new version using the appropriate package manager or build process for your platform
  5. 5. Restore the backed-up configuration files if needed
  6. 6. Start the Apache Traffic Server service
  7. 7. Verify the server is running and the Host header handling works correctly

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

Fix this in Traffic Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-50305 — 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-50305 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