NIOHTTP1 and projects using it for generating HTTP responses can be subject to a HTTP Response Injection attack. This occurs when a HTTP/1.1 server accepts user generated input from an incoming request and reflects it into a HTTP/1.1 response header in some form. A malicious user can add newlines to their input (usually in encoded form) and "inject" those newlines into the returned HTTP response. This capability allows users to work around security headers and HTTP/1.1 framing headers by injecting entirely false responses or other new headers. The injected false responses may also be treated as the response to subsequent requests, which can lead to XSS, cache poisoning, and a number of other flaws. This issue was resolved by adding validation to the HTTPHeaders type, ensuring that there's no whitespace incorrectly present in the HTTP headers provided by users. As the existing API surface is non-failable, all invalid characters are replaced by linear whitespace.
History

Tue, 20 May 2025 20:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


cve-icon MITRE

Status: PUBLISHED

Assigner: Swift

Published: 2022-09-28T19:32:30.000Z

Updated: 2025-05-20T20:02:25.500Z

Reserved: 2022-09-14T00:00:00.000Z

Link: CVE-2022-3215

cve-icon Vulnrichment

Updated: 2024-08-03T01:00:10.853Z

cve-icon NVD

Status : Modified

Published: 2022-09-28T20:15:17.593

Modified: 2025-05-20T20:15:23.553

Link: CVE-2022-3215

cve-icon Redhat

No data.