CVE-2022-31780
Published: 10 August 2022
Summary
CVE-2022-31780 is a high-severity Improper Input Validation (CWE-20) vulnerability in Apache Traffic Server. Its CVSS base score is 7.5 (High).
Operationally, ranked in the top 10.2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
CVE-2022-31780 is an improper input validation flaw in HTTP/2 frame handling that permits request smuggling. The vulnerability affects Apache Traffic Server versions 8.0.0 through 9.1.2 and carries a CVSS 3.1 base score of 7.5.
An unauthenticated network attacker can send crafted HTTP/2 frames to a vulnerable Traffic Server instance and cause subsequent requests to be misinterpreted or routed incorrectly, resulting in integrity impacts such as bypassing access controls or cache poisoning without requiring user interaction.
Advisories from Apache, Debian, and Fedora recommend upgrading to a fixed release of Traffic Server and provide updated packages for supported distributions; the referenced lists detail the specific patched versions and backports available for each platform.
The EPSS score reached a modest peak of 0.0758 before receding to its current value of 0.0483, indicating limited sustained exploitation interest after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-53173
Vulnerability details
Improper Input Validation vulnerability in HTTP/2 frame handling of Apache Traffic Server allows an attacker to smuggle requests. This issue affects Apache Traffic Server 8.0.0 to 9.1.2.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Security testing and developer training directly verify and enforce proper input validation, reducing exploitability of injection and malformed-data weaknesses.
Security testing and evaluation at multiple SDLC stages directly detects missing or flawed input validation, with the required remediation process ensuring fixes are applied.
Directly implements checks on information inputs to reject invalid data before processing.
Spam protection mechanisms perform filtering and detection on inbound/outbound messages, directly compensating for missing or weak input validation of unsolicited content.