CVE-2024-21907: Improper Handling of Exceptional Conditions in Newtonsoft.Json
Newtonsoft.Json before version 13.0.1 is affected by a mishandling of exceptional conditions vulnerability. Crafted data that is passed to the JsonConvert.DeserializeObject method may trigger a StackOverflow exception resulting in denial of service. Depending on the usage of the library, an unauthenticated and remote attacker may be able to cause the denial of service condition.
Security readout for executives and security teams
Plain-English summary
Newtonsoft.Json versions before 13.0.1 can crash while deserializing maliciously shaped JSON. If an internet-facing service accepts untrusted JSON and uses this library path, an unauthenticated remote attacker may be able to cause denial of service.
Executive priority
Treat as a high-priority availability risk for public .NET services. It does not indicate data theft or code execution, but a simple unauthenticated request path may be enough to interrupt service if vulnerable parsing is exposed.
Technical view
The flaw is improper handling of exceptional conditions in JsonConvert.DeserializeObject, producing a StackOverflow exception. CVSS 3.1 is 7.5, network exploitable, low complexity, no privileges or user interaction, with availability impact only. Sources identify a patch before/at 13.0.1.
Likely exposure
Most likely exposure is .NET applications using Newtonsoft.Json before 13.0.1 to deserialize untrusted client-supplied JSON, especially public APIs. The CVE bundle’s affected-version metadata appears incomplete, so confirm against package manifests and advisories.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. Public issue, pull request, commit, GHSA, Snyk, and VulnCheck references document the vulnerability and fix context, but do not prove exploitation in the wild.
Researcher notes
Focus analysis on call paths where attacker-controlled JSON reaches JsonConvert.DeserializeObject. The vulnerability is denial-of-service via stack overflow, so validation should avoid weaponized payloads and instead rely on dependency inventory, code reachability, and controlled regression testing.
Mitigation direction
Upgrade Newtonsoft.Json to 13.0.1 or later where used.
Prioritize internet-facing services that deserialize untrusted JSON.
Check vendor and package advisory guidance before accepting residual risk.
Add request size, depth, and timeout controls where supported.
Redeploy and verify all runtime artifacts use the updated package.
Validation and detection
Inventory NuGet manifests and lockfiles for Newtonsoft.Json below 13.0.1.
Find JsonConvert.DeserializeObject usage reachable from untrusted requests.
Review logs for StackOverflowException, process crashes, or restart loops.
Confirm deployed binaries reference the remediated Newtonsoft.Json version.
Run regression tests around JSON parsing and error handling.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-755: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-755 · source CWE mapping
Improper Handling of Exceptional Conditions
Improper Handling of Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.