GHSA-2gg5-7c4v-6xx2: Axum core Duplicate Of GHSA-m77f-652q-wwp4 Vulnerability

HIGH
Share
CVSS 7.5
CWE-770
Published
Advisory Summary

GHSA-2gg5-7c4v-6xx2 is a HIGH (CVSS 7.5) duplicate of ghsa-m77f-652q-wwp4 vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting Axum core libraries in the crates.io ecosystem. The issue involves duplicate of ghsa-m77f-652q-wwp4. Remediation is available by upgrading affected packages to version 0.2.8, 0.3.0-rc.2.

GHSA-2gg5-7c4v-6xx2 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-2gg5-7c4v-6xx2
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-770: Allocation of Resources Without Limits or Throttling
Affected Product Axum core
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix GHSA-2gg5-7c4v-6xx2

To remediate this vulnerability, upgrade all affected Axum core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

axum-core fixed: 0.2.8 
Upgrade axum-core to 0.2.8
axum-core fixed: 0.3.0-rc.2 
Upgrade axum-core to 0.3.0-rc.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for axum-core

How to Check if You Are Affected

To determine whether your application is affected by GHSA-2gg5-7c4v-6xx2, inspect your project dependencies for Axum core:

inspect dependencies for axum-core

Analyze the terminal output to locate any version of Axum core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.2.8), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. In Axum core, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Duplicate advisory This advisory is a duplicate of [GHSA-m77f-652q-wwp4](https://github.com/advisories/GHSA-m77f-652q-wwp4). This link is maintained to preserve external references. ## Original Description <bytes::Bytes as axum_core::extract::FromRequest>::from_request would not, by default, set a limit for the size of the request body. That meant if a malicious peer would send a very large (or infinite) body your server might run out of memory and crash. This also applies to these extractors which used Bytes::from_request internally: axum::extract::Form axum::extract::Json String

GHSA-2gg5-7c4v-6xx2 Affected Axum core Versions

2 component(s)
Fixed Versions:
0.2.80.3.0-rc.2
Product / Package Ecosystem Affected Versions Fixed Version
axum-core
 crates.io
< 0.2.8
0.2.8
axum-core
 crates.io
≥ 0.3.0-rc.1
< 0.3.0-rc.2
All 1 versions
0.3.0-rc.1
0.3.0-rc.2

References

NVD — GHSA-2gg5-7c4v-6xx2 NVD
https://nvd.nist.gov/vuln/detail/CVE-2022-3212
research.jfrog.com/vulnerabilities/axu... WEB
https://research.jfrog.com/vulnerabilities/axum-core-dos
rustsec.org/advisories/rustsec-... WEB
https://rustsec.org/advisories/RUSTSEC-2022-0055.html

Frequently Asked Questions

What is GHSA-2gg5-7c4v-6xx2?
GHSA-2gg5-7c4v-6xx2 is a security vulnerability in Axum core involving Duplicate of GHSA-m77f-652q-wwp4 under CWE-770: Allocation of Resources Without Limits or Throttling.
Which Axum core versions are affected?
Affected versions include releases prior to 0.2.8, 0.3.0-rc.2 across affected packages: axum-core.
What version fixes GHSA-2gg5-7c4v-6xx2?
Upgrading to 0.2.8, 0.3.0-rc.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is axum-core affected?
Yes, axum-core is affected in releases prior to 0.2.8, 0.3.0-rc.2. Upgrade your dependency to 0.2.8, 0.3.0-rc.2 or later.
What is the CVSS score of GHSA-2gg5-7c4v-6xx2?
GHSA-2gg5-7c4v-6xx2 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with GHSA-2gg5-7c4v-6xx2?
GHSA-2gg5-7c4v-6xx2 is classified under CWE-770: Allocation of Resources Without Limits or Throttling (The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.).
How can I check crates.io dependencies for GHSA-2gg5-7c4v-6xx2?
Run the dependency tree command: 'inspect dependencies for axum-core'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2gg5-7c4v-6xx2",
  "modified" : "2022-09-19T20:19:08Z",
  "published" : "2022-09-15T00:00:19Z",
  "withdrawn" : "2022-09-16T20:59:09Z",
  "aliases" : [ ],
  "summary" : "Duplicate of GHSA-m77f-652q-wwp4",
  "details" : "## Duplicate advisory\nThis advisory is a duplicate of [GHSA-m77f-652q-wwp4](https://github.com/advisories/GHSA-m77f-652q-wwp4). This link is maintained to preserve external references.\n\n## Original Description\n<bytes::Bytes as axum_core::extract::FromRequest>::from_request would not, by default, set a limit for the size of the request body. That meant if a malicious peer would send a very large (or infinite) body your server might run out of memory and crash. This also applies to these extractors which used Bytes::from_request internally: axum::extract::Form axum::extract::Json String",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "axum-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.2.8"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "axum-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.3.0-rc.1"
      }, {
        "fixed" : "0.3.0-rc.2"
      } ]
    } ],
    "versions" : [ "0.3.0-rc.1" ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-3212"
  }, {
    "type" : "WEB",
    "url" : "https://research.jfrog.com/vulnerabilities/axum-core-dos"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2022-0055.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-770" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-09-16T20:59:09Z",
    "nvd_published_at" : "2022-09-14T16:15:00Z"
  }
}