CVE-2022-3212Public exploitNetwork attack vector

Service crash via unbounded request-body allocation

Published Sep 14, 2022 · Updated Aug 3, 2024

Resource exhaustion in Tokio axum-core before 0.2.8 and 0.3.0-rc.1 allows remote attackers to crash servers via crafted HTTP requests. The Bytes FromRequest implementation trusts an attacker-controlled Content-Length and attempts an unbounded body allocation; Form, Json, and String inherit the same behavior. An unauthenticated request reaching a handler that uses one of these extractors can panic the Rust allocator and terminate the process, interrupting service without data access or modification.

CVSS severity7.5
High
EPSS probability0.98%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Resource exhaustion in Tokio axum-core before 0.2.8 and 0.3.0-rc.1 allows remote attackers to crash servers via crafted HTTP requests. The Bytes FromRequest implementation trusts an attacker-controlled Content-Length and attempts an unbounded body allocation; Form, Json, and String inherit the same behavior. An unauthenticated request reaching a handler that uses one of these extractors can panic the Rust allocator and terminate the process, interrupting service without data access or modification.

The record

CVE
CVE-2022-3212
Published
Sep 14, 2022
Updated
Aug 3, 2024
Vendor
Tokio
Product
axum-core
Classifications
CWE-770, T1499.003
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Sep 14, 2022CVE publishedPublication date reported by the CVE source.
  2. Aug 3, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0.3.0-rc.1
  2. Affected versionversion=unspecified <0.2.8

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Tokio · axum-coreversion=0.3.0-rc.1; version=unspecified <0.2.8

Published CVSS scores

7.5GitHub Advisory DatabaseCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
7.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-770Allocation of Resources Without Limits or Throttling
T1499.003Application Exhaustion Flood

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo