CVE-2022-3215
Last modified
CVE-2022-3215 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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. EPSS estimates a 0.54% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apple | Swiftnio | < 2.29.1 |
| Apple | Swiftnio | >= 2.30.0, < 2.39.1 |
| Apple | Swiftnio | >= 2.40.0, < 2.42.0 |
References
- https://github.com/apple/swift-nio/security/advisories/GHSA-7fj7-39wj-c64fThird Party Advisory
- https://github.com/apple/swift-nio/security/advisories/GHSA-7fj7-39wj-c64fThird Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-3215?
How severe is CVE-2022-3215?
How do I fix CVE-2022-3215?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-32143In multiple CODESYS products, file download and upload funct…8.8
- CVE-2022-32144There is an insufficient input verification vulnerability in…8.6
- CVE-2022-32145A vulnerability has been identified in Teamcenter Active Wor…6.1
- CVE-2022-32147Rejected reason: reserved but not needed
- CVE-2022-32148Improper exposure of client IP addresses in net/http before …6.5
- CVE-2022-32149An attacker may cause a denial of service by crafting an Acc…7.5
- CVE-2022-32150Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMB…
- CVE-2022-32151The httplib and urllib Python libraries that Splunk shipped …9.1
- CVE-2022-32152Splunk Enterprise peers in Splunk Enterprise versions before…7.2
- CVE-2022-32153Splunk Enterprise peers in Splunk Enterprise versions before…8.1
- CVE-2022-32154Dashboards in Splunk Enterprise versions before 9.0 might le…8.1
- CVE-2022-32155In universal forwarder versions before 9.0, management servi…7.5
Are you affected by CVE-2022-3215?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
