cve.bz

CVE-2021-41084 typelevel http4s: Injection

4.7 mediumExploit referenceEPSS 1.2%Fix available

Medium (4.7) in typelevel http4s. EPSS 1.2% estimated probability of exploitation activity in the next 30 days. Fixed in org.http4s:http4s-client_2.12 0.21.29, 0.22.5, 0.23.4.

On this page
http4s is an open source scala interface for HTTP. In affected versions http4s is vulnerable to response-splitting or request-splitting attacks when untrusted user input is used to create any of the following fields: Header names (`Header.name`å), Header values (`Header.value`), Status reason phrases (`Status.reason`), URI paths (`Uri.Path`), URI authority registered names (`URI.RegName`) (through 0.21). This issue has been resolved in versions 0.21.30, 0.22.5, 0.23.4, and 1.0.0-M27 perform the following. As a matter of practice http4s services and client applications should sanitize any user input in the aforementioned fields before returning a request or response to the backend. The carriage return, newline, and null characters are the most threatening.

Severity

CVSS 3.1

4.7 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N
EPSS
1.2% (unchanged from 1.2% a week ago; 1.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 70th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component (Injection)
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control, A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2021-41084 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-41084?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-41084?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2021-41084 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
typelevel:http4sbefore 0.21.29
typelevel:http4sfrom 0.22.0 before 0.22.5
typelevel:http4sfrom 0.23.0 before 0.23.4
typelevel:http4s1.0.0:milestone1
typelevel:http4s1.0.0:milestone10
typelevel:http4s1.0.0:milestone11
typelevel:http4s1.0.0:milestone12
typelevel:http4s1.0.0:milestone13
typelevel:http4s1.0.0:milestone14
typelevel:http4s1.0.0:milestone15
typelevel:http4s1.0.0:milestone16
typelevel:http4s1.0.0:milestone17
typelevel:http4s1.0.0:milestone18
typelevel:http4s1.0.0:milestone19
typelevel:http4s1.0.0:milestone2
typelevel:http4s1.0.0:milestone20
typelevel:http4s1.0.0:milestone21
typelevel:http4s1.0.0:milestone22
typelevel:http4s1.0.0:milestone23
typelevel:http4s1.0.0:milestone24
typelevel:http4s1.0.0:milestone25
typelevel:http4s1.0.0:milestone26
typelevel:http4s1.0.0:milestone3
typelevel:http4s1.0.0:milestone4
typelevel:http4s1.0.0:milestone5
typelevel:http4s1.0.0:milestone6
typelevel:http4s1.0.0:milestone7
typelevel:http4s1.0.0:milestone8
typelevel:http4s1.0.0:milestone9

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-5vcm-3xc3-w7x3Mavenorg.http4s:http4s-client_2.12<0.21.290.21.29
GHSA-5vcm-3xc3-w7x3Mavenorg.http4s:http4s-client_2.12>=0.22.0 <0.22.50.22.5
GHSA-5vcm-3xc3-w7x3Mavenorg.http4s:http4s-client_2.12>=0.23.0 <0.23.40.23.4
GHSA-5vcm-3xc3-w7x3Mavenorg.http4s:http4s-client_2.13<0.21.290.21.29
GHSA-5vcm-3xc3-w7x3Mavenorg.http4s:http4s-client_2.13>=0.22.0 <0.22.50.22.5
GHSA-5vcm-3xc3-w7x3Mavenorg.http4s:http4s-client_2.13>=0.23.0 <0.23.40.23.4
GHSA-5vcm-3xc3-w7x3Mavenorg.http4s:http4s-client_3<0.21.290.21.29
GHSA-5vcm-3xc3-w7x3Mavenorg.http4s:http4s-client_3>=0.22.0 <0.22.50.22.5
GHSA-5vcm-3xc3-w7x3Mavenorg.http4s:http4s-client_3>=0.23.0 <0.23.40.23.4
GHSA-5vcm-3xc3-w7x3Mavenorg.http4s:http4s-server_2.10<=0.21.28no fix published
GHSA-5vcm-3xc3-w7x3Mavenorg.http4s:http4s-server_2.11<=0.21.28no fix published
GHSA-5vcm-3xc3-w7x3Mavenorg.http4s:http4s-server_2.12<0.21.290.21.29
GHSA-5vcm-3xc3-w7x3Mavenorg.http4s:http4s-server_2.12>=0.22.0 <0.22.50.22.5
GHSA-5vcm-3xc3-w7x3Mavenorg.http4s:http4s-server_2.12>=0.23.0 <0.23.40.23.4
GHSA-5vcm-3xc3-w7x3Mavenorg.http4s:http4s-server_2.13<0.21.290.21.29
GHSA-5vcm-3xc3-w7x3Mavenorg.http4s:http4s-server_2.13>=0.22.0 <0.22.50.22.5
GHSA-5vcm-3xc3-w7x3Mavenorg.http4s:http4s-server_2.13>=0.23.0 <0.23.40.23.4
GHSA-5vcm-3xc3-w7x3Mavenorg.http4s:http4s-server_2.13.0-M5<=0.21.28no fix published
GHSA-5vcm-3xc3-w7x3Mavenorg.http4s:http4s-server_3>=0.22.0 <0.22.50.22.5
GHSA-5vcm-3xc3-w7x3Mavenorg.http4s:http4s-server_3>=0.23.0 <0.23.40.23.4

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-74 (37).

References

Check your stackJSON