Cyber Resilience

CVE-2024-50306

Apache Traffic Server 9.0.0 – 9.2.6

Published
14 November 2024
Modified
03 November 2025
Patch / advisory
CVSS Score v3.1 9.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
EPSS Score 0.016 73th percentile
Risk Priority 73 floored blend · peak EPSS

Summary

CVE-2024-50306 is a critical-severity Unchecked Return Value (CWE-252) vulnerability in Apache Traffic Server. Its CVSS base score is 9.1 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 27% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Unchecked return value can allow Apache Traffic Server to retain privileges on startup. This issue affects Apache Traffic Server: from 9.2.0 through 9.2.5, from 10.0.0 through 10.0.1. Users are recommended to upgrade to version 9.2.6 or 10.0.2, which fixes the…

more

issue.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-58185Same product: Apache Traffic Server
CVE-2026-33930Same product: Apache Traffic Server
CVE-2026-58158Same product: Apache Traffic Server
CVE-2026-58180Same product: Apache Traffic Server
CVE-2026-58179Same product: Apache Traffic Server
CVE-2026-58181Same product: Apache Traffic Server
CVE-2026-58164Same product: Apache Traffic Server
CVE-2024-50305Same product: Apache Traffic Server
CVE-2026-58188Same product: Apache Traffic Server
CVE-2026-58177Same product: Apache Traffic Server

Affected Assets

apache
traffic server
9.0.0 — 9.2.6 · 10.0.0 — 10.0.2

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and code evaluation can discover instances where return values are ignored.

Requiring a documented development process and coding standards can mandate explicit checking of all function return values.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require checking and handling all function return values to detect error conditions.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development and acceptance can detect missing return-value checks.

prevents

Secure development life cycle mandates verification of return values to prevent undetected failures.

prevents

Application security requirements include input/output validation and error handling that covers return-value checks.

degrades

Secure system architecture and engineering principles require robust error handling and defensive coding practices.

prevents

Secure coding explicitly requires checking return values to avoid CWE-252.

References