CVE-2022-47185 | Apache Traffic Server: Invalid Range header causes a crash

Improper input validation vulnerability on the range header in Apache Software Foundation Apache Traffic Server.This issue affects Apache Traffic Server: through 9.2.1.

Published: 2023-08-09 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2022-47185 is rated Moderate Risk (55.7/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.49%). Mandatory action: Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-47185

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.56% 1.49% +0.93%
2 2026-06-05 0.52% 0.56% +0.04%
3 2026-05-04 0.52%

Full EPSS history (21 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-47185

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9 3.6 [email protected]
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2022-47185

OS Trackers for CVE-2022-47185

vendor priority summary link
debian not yet assigned CVE-2022-47185 not yet assigned priority: Debian including 1 source packages (trafficserver), 3 status rows across 3 suites (bookworm, bullseye, sid): resolved 3. https://security-tracker.debian.org/tracker/CVE-2022-47185
ubuntu medium CVE-2022-47185 medium priority: Ubuntu including 1 source packages (trafficserver), 12 status rows across 12 suites (bionic, focal, jammy, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 4, ignored 3, needs-triage 3, needed 1, released 1. https://ubuntu.com/security/CVE-2022-47185

Affected software / configurations for CVE-2022-47185

Vendor Product Version Raw CPE
apache traffic_server >= 8.0.0, <= 8.1.7 cpe:2.3:a:apache:traffic_server:*:*:*:*:*:*:*:*
apache traffic_server >= 9.0.0, <= 9.2.1 cpe:2.3:a:apache:traffic_server:*:*:*:*:*:*:*:*

References for CVE-2022-47185

cvelogic Threat Intelligence