LiveActive security incident?Get immediate response
CVE Record

CVE-2022-31150: CRLF injection in request headers

undici is an HTTP/1.1 client, written from scratch for Node.js. It is possible to inject CRLF sequences into request headers in undici in versions less than 5.7.1. A fix was released in version 5.8.0. Sanitizing all HTTP headers from untrusted sources to eliminate `\r\n` is a workaround for this issue.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-31150 affects undici, a Node.js HTTP/1.1 client. If an application lets untrusted input influence outbound request headers, an attacker may inject line breaks into those headers. The documented impact is limited integrity risk, not data theft or service outage, but exposed services should still update or sanitize inputs.

Executive priority

Prioritize normal patch-cycle remediation unless the application processes untrusted input into outbound headers. Raise urgency for internet-facing services, multi-tenant systems, or vendor appliances where affected undici versions are confirmed.

Technical view

The issue is CWE-93 CRLF injection in undici request headers. The source bundle reports vulnerable undici versions below 5.7.1 and a fix released in 5.8.0. CVSS 3.1 is 5.3, network exploitable, low complexity, no privileges or user interaction, unchanged scope, integrity low.

Likely exposure

Exposure is most likely in Node.js applications or products that directly or transitively use undici and create outbound HTTP headers from user-controlled or external data. The bundle also includes a NetApp advisory, suggesting downstream product impact may exist and should be checked with vendors.

Exploitation context

The provided data does not show active exploitation, and KEV is false. Exploitation would require a reachable application path where attacker-influenced data is copied into undici request headers without CRLF sanitization. Do not assume exploitability from package presence alone.

Researcher notes

Evidence is sufficient for affected component, weakness class, CVSS, workaround, and fixed release. The version boundary in the bundle mentions both below 5.7.1 and fix release 5.8.0; verify exact package exposure against the GitHub advisory and installed dependency metadata.

Mitigation direction

  • Upgrade undici to the vendor fixed release, version 5.8.0 or later.
  • Sanitize all untrusted HTTP header values to remove CRLF sequences.
  • Review downstream vendor advisories for embedded undici usage.
  • Rebuild and redeploy affected containers or packages after dependency updates.

Validation and detection

  • Check lockfiles and SBOMs for undici versions in production builds.
  • Confirm scanners no longer report CVE-2022-31150 after remediation.
  • Review code paths that set outbound HTTP headers from external input.
  • Add tests that reject CRLF in untrusted header values.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-93: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-31150 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2022-31150Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
nodejsundici< v5.7.1, >= v5.8.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-93 · source CWE mapping

Improper Neutralization of CRLF Sequences ('CRLF Injection')

Improper Neutralization of CRLF Sequences ('CRLF Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.