GHSA-7fj7-39wj-c64f SwiftNIO vulnerable to Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting')

• SwiftURL github.com/apple/swift-nio: >= 2.41.0, < 2.42.0 → fixed in 2.42.0 • SwiftURL github.com/apple/swift-nio: >= 2.39.0, < 2.39.1 → fixed in 2.39.1 • SwiftURL github.com/apple/swift-nio: < 2.29.1 → fixed in 2.29.1

`NIOHTTP1` and projects using it for generating HTTP responses, including SwiftNIO, 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 a default channel handler that polices outbound headers. This channel handler is added by default to channel pipelines, but can be removed by users if they are doing this validation themselves.