cve.bz

CVE-2023-22465 typelevel http4s: Improper Input Validation

5.3 mediumExploit referenceEPSS 0.9%Fix available

Medium (5.3) in typelevel http4s. EPSS 0.9% estimated probability of exploitation activity in the next 30 days. Fixed in org.http4s:http4s-core_2.13 0.21.34, 0.22.15, 0.23.17.

On this page
Http4s is a Scala interface for HTTP services. Starting with version 0.1.0 and prior to versions 0.21.34, 0.22.15, 0.23.17, and 1.0.0-M38, the `User-Agent` and `Server` header parsers are susceptible to a fatal error on certain inputs. In http4s, modeled headers are lazily parsed, so this only applies to services that explicitly request these typed headers. Fixes are released in 0.21.34, 0.22.15, 0.23.17, and 1.0.0-M38. As a workaround, use the weakly typed header interface.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.9% (unchanged from 0.9% a week ago; 0.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 60th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2025-03-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-20 Improper Input Validation
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • org.http4s:http4s-core_2.13 (Maven): fixed in 0.21.34, 0.22.15, 0.23.17, 1.0.0-M38
  • org.http4s:http4s-core_2.12 (Maven): fixed in 0.21.34, 0.22.15, 0.23.17

Ask an AI about this CVE

Show the promptExplain CVE-2023-22465 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-22465?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-22465?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-2023-22465 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:http4sfrom 0.1.0 before 0.21.34
typelevel:http4sfrom 0.22.0 before 0.22.15
typelevel:http4sfrom 0.23.0 before 0.23.17
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:milestone27
typelevel:http4s1.0.0:milestone28
typelevel:http4s1.0.0:milestone29
typelevel:http4s1.0.0:milestone3
typelevel:http4s1.0.0:milestone30
typelevel:http4s1.0.0:milestone31
typelevel:http4s1.0.0:milestone32
typelevel:http4s1.0.0:milestone33
typelevel:http4s1.0.0:milestone34
typelevel:http4s1.0.0:milestone35
typelevel:http4s1.0.0:milestone36
typelevel:http4s1.0.0:milestone37
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-54w6-vxfh-fw7fMavenorg.http4s:http4s-core_2.13>=0.1.0 <0.21.340.21.34
GHSA-54w6-vxfh-fw7fMavenorg.http4s:http4s-core_2.13>=0.22.0 <0.22.150.22.15
GHSA-54w6-vxfh-fw7fMavenorg.http4s:http4s-core_2.13>=0.23.0 <0.23.170.23.17
GHSA-54w6-vxfh-fw7fMavenorg.http4s:http4s-core_2.13>=1.0.0-M1 <1.0.0-M381.0.0-M38
GHSA-54w6-vxfh-fw7fMavenorg.http4s:http4s-core_2.10>=0.1.0 <=0.9.3no fix published
GHSA-54w6-vxfh-fw7fMavenorg.http4s:http4s-core_2.11>=0.1.0 <=0.21.0-M1no fix published
GHSA-54w6-vxfh-fw7fMavenorg.http4s:http4s-core_2.12>=0.1.0 <0.21.340.21.34
GHSA-54w6-vxfh-fw7fMavenorg.http4s:http4s-core_2.12>=0.22.0 <0.22.150.22.15
GHSA-54w6-vxfh-fw7fMavenorg.http4s:http4s-core_2.12>=0.23.0 <0.23.170.23.17
GHSA-54w6-vxfh-fw7fMavenorg.http4s:http4s-core>=1.0.0-M1 <=1.0.0-M30no fix published

Attack patterns (CAPEC)

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

References

Check your stackJSON