[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fcAbeNFNP5SvD7r6MvlwQbWDhr7kRI06Yz9yHa6mQnzw":3,"g5a-risk:CVE-2022-3215":117},{"success":4,"data":5,"meta":114},true,{"cveId":6,"title":7,"description":8,"shortDescription":9,"publishedDate":10,"lastModified":11,"cvssScore":12,"cvssVector":13,"cvssMetrics":14,"epssScore":33,"epssPercentile":26,"epssTimeSeries":34,"severity":36,"affectedProducts":37,"affectedProductsCount":43,"references":44,"referencesCount":52,"weaknesses":53,"weaknessesCount":52,"isActivelyExploited":68,"cisaInfo":26,"otxData":26,"relatedBlogPosts":69,"seoMetadata":70,"configurations":95,"relatedVendorCves":112,"notableEvents":113},"CVE-2022-3215","What is CVE-2022-3215?","NIOHTTP1 and projects using it for generating HTTP responses can be subject to a HTTP Response Injection attack. This occurs when a HTTP\u002F1.1 server accepts user generated input from an incoming request and reflects it into a HTTP\u002F1.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\u002F1.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.","NIOHTTP1 and projects using it for generating HTTP responses can be subject to a HTTP Response Injection attack. This occurs when a HTTP\u002F1.1 server accepts u...","2022-09-28T20:15:17.593","2025-05-20T20:15:23.553",7.5,"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:N\u002FI:H\u002FA:N",{"CVSSMetricV31":15,"CVSSMetricV30":26,"CVSSMetricV2":26,"CVSSMetricV40":26},[16,29],{"Source":17,"Type":18,"CVSSData":19,"ExploitabilityScore":27,"ImpactScore":28},"nvd@nist.gov","Primary",{"Version":20,"VectorString":13,"AttackVector":21,"AttackComplexity":22,"PrivilegesRequired":23,"UserInteraction":23,"Scope":24,"ConfidentialityImpact":23,"IntegrityImpact":25,"AvailabilityImpact":23,"BaseScore":12,"BaseSeverity":25,"ExploitCodeMaturity":26,"RemediationLevel":26,"ReportConfidence":26,"TemporalScore":26,"TemporalSeverity":26,"ConfidentialityRequirement":26,"IntegrityRequirement":26,"AvailabilityRequirement":23,"ModifiedAttackVector":26,"ModifiedAttackComplexity":26,"ModifiedPrivilegesRequired":26,"ModifiedUserInteraction":26,"ModifiedScope":26,"ModifiedConfidentialityImpact":26,"ModifiedIntegrityImpact":26,"ModifiedAvailabilityImpact":26,"EnvironmentalScore":26,"EnvironmentalSeverity":26},"3.1","NETWORK","LOW","NONE","UNCHANGED","HIGH",null,3.9,3.6,{"Source":30,"Type":31,"CVSSData":32,"ExploitabilityScore":27,"ImpactScore":28},"134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary",{"Version":20,"VectorString":13,"AttackVector":21,"AttackComplexity":22,"PrivilegesRequired":23,"UserInteraction":23,"Scope":24,"ConfidentialityImpact":23,"IntegrityImpact":25,"AvailabilityImpact":23,"BaseScore":12,"BaseSeverity":25,"ExploitCodeMaturity":26,"RemediationLevel":26,"ReportConfidence":26,"TemporalScore":26,"TemporalSeverity":26,"ConfidentialityRequirement":26,"IntegrityRequirement":26,"AvailabilityRequirement":23,"ModifiedAttackVector":26,"ModifiedAttackComplexity":26,"ModifiedPrivilegesRequired":26,"ModifiedUserInteraction":26,"ModifiedScope":26,"ModifiedConfidentialityImpact":26,"ModifiedIntegrityImpact":26,"ModifiedAvailabilityImpact":26,"EnvironmentalScore":26,"EnvironmentalSeverity":26},0.00664,[35,35,35,35,35,33,33],0.00649,"High",[38],{"vendor":39,"product":40,"version":41,"criteria":42,"vulnerable":4},"apple","swiftnio","*","cpe:2.3:a:apple:swiftnio:*:*:*:*:*:*:*:*",1,[45,50],{"url":46,"source":47,"tags":48},"https:\u002F\u002Fgithub.com\u002Fapple\u002Fswift-nio\u002Fsecurity\u002Fadvisories\u002FGHSA-7fj7-39wj-c64f","GitHub",[49],"Third Party Advisory",{"url":46,"source":47,"tags":51},[49],2,[54,62],{"id":55,"name":56,"description":57,"extendedDescription":58,"status":59,"abstraction":60,"structure":61},"CWE-113","Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request\u002FResponse Splitting')","The product receives data from an HTTP agent\u002Fcomponent (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers.","HTTP agents or components may include a web server, load balancer, reverse proxy, web caching proxy, application firewall, web browser, etc. Regardless of the role, they are expected to maintain coherent, consistent HTTP communication state across all components. However, including unexpected data in an HTTP header allows an attacker to specify the entirety of the HTTP message that is rendered by the client HTTP agent (e.g., web browser) or back-end HTTP agent (e.g., web server), whether the message is part of a request or a response.\nWhen an HTTP request contains unexpected CR and LF characters, the server may respond with an output stream that is interpreted as \"splitting\" the stream into two different HTTP messages instead of one. CR is carriage return, also given by %0d or \\r, and LF is line feed, also given by %0a or \\n.\nIn addition to CR and LF characters, other valid\u002FRFC compliant special characters and unique character encodings can be utilized, such as HT (horizontal tab, also given by %09 or \\t) and SP (space, also given as + sign or %20).\nThese types of unvalidated and unexpected data in HTTP message headers allow an attacker to control the second \"split\" message to mount attacks such as server-side request forgery, cross-site scripting, and cache poisoning attacks.\nHTTP response splitting weaknesses may be present when:","Incomplete","Variant","Simple",{"id":63,"name":64,"description":65,"extendedDescription":66,"status":59,"abstraction":67,"structure":61},"CWE-74","Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')","The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.","Software or other automated logic has certain assumptions about what constitutes data and control respectively. It is the lack of verification of these assumptions for user-controlled input that leads to injection problems. Injection problems encompass a wide variety of issues -- all mitigated in very different ways and usually attempted in order to alter the control flow of the process. For this reason, the most effective way to discuss these weaknesses is to note the distinct features that classify them as injection weaknesses. The most important issue to note is that all injection problems share one thing in common -- i.e., they allow for the injection of control plane data into the user-controlled data plane. This means that the execution of the process may be altered by sending code in through legitimate data channels, using no other mechanism. While buffer overflows, and many other flaws, involve the use of some further issue to gain execution, injection problems need only for the data to be parsed.","Class",false,[],{"title":71,"metaDescription":72,"keywords":73,"canonicalUrl":74,"structuredData":75},"What is CVE-2022-3215? Vulnerability Analysis | Security Advisory | Precursor Intelligence","Comprehensive analysis of CVE-2022-3215, a high severity cyber security vulnerability from 2022. NIOHTTP1 and projects using it for generating HTTP responses...","CVE-2022-3215, CVE-2022-3215 vulnerability, CVE-2022-3215 security, high severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research, vulnerability assessment, cyber threats, 2022, CVSS score, exploit, patch, remediation, apple security, swiftnio vulnerability","\u002Fwhat-is\u002Fcve-2022-3215",{"@context":76,"@type":77,"headline":71,"description":72,"datePublished":10,"dateModified":11,"author":78,"publisher":82,"about":86,"mainEntityOfPage":90,"articleSection":93,"keywords":94},"https:\u002F\u002Fschema.org","TechArticle",{"@type":79,"name":80,"url":81},"Organization","Precursor Intelligence","https:\u002F\u002Fprecursorintelligence.com",{"@type":79,"name":80,"url":81,"logo":83},{"@type":84,"url":85},"ImageObject","https:\u002F\u002Fprecursorintelligence.com\u002Fimg\u002Flogos\u002Feplogo.png",{"@type":87,"name":6,"description":88,"additionalType":89},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":91,"@id":92},"WebPage","https:\u002F\u002Fprecursorintelligence.com\u002Fwhat-is\u002Fcve-2022-3215","Cybersecurity","CVE-2022-3215, CVE-2022-3215 vulnerability, CVE-2022-3215 security, high severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research",[96],{"Operator":26,"Negate":26,"Nodes":97},[98],{"Operator":99,"Negate":26,"CPEMatch":100},"OR",[101,104,108],{"Vulnerable":4,"Criteria":42,"MatchCriteriaID":102,"VersionStartExcluding":26,"VersionStartIncluding":26,"VersionEndExcluding":103,"VersionEndIncluding":26},"7DE92207-1814-4053-ABD1-36CFF3BB8BF8","2.29.1",{"Vulnerable":4,"Criteria":42,"MatchCriteriaID":105,"VersionStartExcluding":26,"VersionStartIncluding":106,"VersionEndExcluding":107,"VersionEndIncluding":26},"42384BB2-84B3-4DCB-A215-4F21D058A833","2.30.0","2.39.1",{"Vulnerable":4,"Criteria":42,"MatchCriteriaID":109,"VersionStartExcluding":26,"VersionStartIncluding":110,"VersionEndExcluding":111,"VersionEndIncluding":26},"F1D8C095-CF99-4ED4-96C8-DD0396D5509D","2.40.0","2.42.0",[],[],{"lastModified":11,"cacheTime":115,"version":116},1792265531305,"2.0",{"score":118,"band":119,"action":120,"scoredAt":121},46,"Medium","Plan remediation","2026-10-16T06:55:51.754217+00:00"]