dbcve.org
Serde Json WasmApplication · Cosmwasm

CVE-2024-58264

HIGH · 7.5 CVSS v3.1 Published 2025-07-27
Fix available
A fix is available. Upgrade to 1.0.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The serde-json-wasm crate before 1.0.1 for Rust allows stack consumption via deeply nested JSON data.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The serde-json-wasm crate before version 1.0.1 for Rust is vulnerable to stack exhaustion when parsing deeply nested JSON data. This occurs because the recursive JSON parsing implementation consumes stack space for each nesting level without adequate limits, allowing an attacker to cause a stack overflow and denial of service by providing specially crafted deeply nested JSON input.

MitigationUpgrade serde-json-wasm to version 1.0.1 or later, which should include bounds checking or iterative parsing to limit recursion depth. Validate and limit the maximum nesting depth of untrusted JSON input as an additional defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Serde Json WasmApplication
Affected:< 1.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate serde-json-wasm in your project dependencies
    Search your project's Cargo.toml file for 'serde-json-wasm' in the [dependencies] section, and check your Cargo.lock file for the installed version entry
    Affected if serde-json-wasm is present with a version lower than 1.0.1 (such as 1.0.0 or any version starting with 0.x)
  2. Identify JSON parsing code that uses serde-json-wasm
    Search your codebase for imports or usage of serde-json-wasm's 'from_str', 'from_slice', or similar deserialization functions
    Affected if The crate is directly used for parsing JSON data in your code
  3. Determine if untrusted or external JSON input is processed
    Review the data flow feeding into serde-json-wasm parsing calls: check if input comes from network requests, uploaded files, user-provided data, or any source outside the application's trusted boundary
    Affected if JSON input originates from untrusted sources (network, user upload, external APIs) without prior sanitization
  4. Assess whether deeply nested JSON could be supplied
    Check if there are any application-level limits on JSON nesting depth, or if any validation occurs before passing data to serde-json-wasm's parsing functions
    Affected if No depth limits are enforced on incoming JSON and deeply nested structures could reach the parser

You are affected if your project uses serde-json-wasm version below 1.0.1 and processes untrusted or potentially deeply nested JSON input without application-level nesting depth limits.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.1 or later
Fixed in 1.0.1
Interim mitigation

Upgrade serde-json-wasm to version 1.0.1 or later, which should include bounds checking or iterative parsing to limit recursion depth. Validate and limit the maximum nesting depth of untrusted JSON input as an additional defense-in-depth measure.

Recommended fix High confidence

serde-json-wasm version 1.0.1

  1. Update the serde-json-wasm dependency in your Cargo.toml file to version 1.0.1 or later: serde-json-wasm = "1.0.1"
  2. Run `cargo update serde-json-wasm` or `cargo build` to fetch the fixed version
  3. Run your test suite to verify the upgrade does not break existing functionality

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Serde Json Wasm Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-58264 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-58264 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data