VDB

CVE-2022-3215

CVE-2022-3215 PUBLISHED CVSS 5.300000190734863 MEDIUM

Reported by swift · Published September 28, 2022

github.com/apple/swift-nio is fixed in 2.42.0, 2.39.1 and 2.29.1 (GitHub Packages)

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
github.com/apple/swift-nioGitHub Packages2.42.0, 2.39.1, 2.29.1
github.com/apple/swift-nioswiftpackageindex.com2.42.0, 2.39.1, 2.29.1
swiftnioapple2.42.0, 2.39.1, 2.29.1
SwiftNIOSwift Project2.41.2

Risk scores

CVSS 3.1
5.300000190734863
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected products

VendorProductVersions
Swift ProjectSwiftNIOunspecified
Swift ProjectSwiftNIO*
github.comapple/swift-nio2.41.0, 2.39.0, 0

Timeline

  • Sep 28, 2022 CVE Published
  • Sep 29, 2022 EPSS Score (30 in total, the first dated here)
  • Apr 3, 2026 Security Advisory
  • Jun 17, 2026 CVE Updated
  • Jun 24, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2022-3215
vulnetix vdb fixes CVE-2022-3215

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2022-3215/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›