← Vulnerability feed

Vulnerability record · CVE-2013-3861 · published 9 October 2013

CVE-2013-3861: Microsoft .NET Framework JSON parsing denial of service

Microsoft · .Net Framework

Microsoft .NET Framework 2.0 SP2, 3.5, 3.5 SP1, 3.5.1, 4, and 4.5 fail to properly validate crafted character sequences in JSON data, causing an application crash or hang. The flaw is an input validation issue in JSON parsing that lets unauthenticated remote attackers degrade availability of .NET applications that process attacker-supplied JSON.

7.8 CVSS 2.0 High EPSS 82% · top 0.3% CWE-20 · Improper input validation
7.8CVSS 2.0 base score
82%EPSS exploitation probability, 30 days
NoNot in CISA KEV
1Affected product versions listed by NVD
6References
16 Jun 2026Last modified by NVD

Description

Microsoft .NET Framework 2.0 SP2, 3.5, 3.5 SP1, 3.5.1, 4, and 4.5 allows remote attackers to cause a denial of service (application crash or hang) via crafted character sequences in JSON data, aka "JSON Parsing Vulnerability."

AV:N/AC:L/Au:N/C:N/I:N/A:C

Automated analysis

Generated by VULONE's analysis model from the NVD record, CISA KEV and EPSS data on 18 September 2026. Confidence: medium.

high priorityRemote, unauthenticated availability impact across widely deployed .NET Framework versions, with very high EPSS despite no KEV listing.

What it is

Microsoft .NET Framework 2.0 SP2, 3.5, 3.5 SP1, 3.5.1, 4, and 4.5 fail to properly validate crafted character sequences in JSON data, causing an application crash or hang. The flaw is an input validation issue in JSON parsing that lets unauthenticated remote attackers degrade availability of .NET applications that process attacker-supplied JSON.

Impact

An attacker can crash or hang the affected .NET application, denying service to legitimate users. There is no confidentiality or integrity impact; only availability is affected.

Attack surface

Reachable over the network (AV:N) with no authentication (Au:N) and no user interaction, wherever an application passes untrusted JSON into the vulnerable .NET Framework parser. The record does not identify specific entry points beyond JSON data handling.

Exploitation

Not listed in CISA KEV and no public exploit references are tagged in the record, but EPSS is very high (0.82444, 99.6th percentile), indicating elevated predicted exploitation likelihood.

What to do

  • Apply Microsoft security bulletin MS13-082 for the affected .NET Framework versions.
  • Validate and constrain JSON input size and character content before parsing in .NET applications.
  • Isolate or rate-limit services that accept untrusted JSON to limit denial-of-service blast radius.
  • Monitor for and restart hung or crashed .NET application processes as a stopgap where patching is delayed.

Detection

  • Monitor .NET application logs for repeated unhandled exceptions or crashes tied to JSON parsing.
  • Alert on process hangs or worker thread stalls in .NET services following inbound JSON requests.
  • Watch for spikes in malformed or unusual character sequences in JSON payloads reaching .NET endpoints.

This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.

Affected products

1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.

References

Track CVE-2013-3861 inside VULONE

Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.

Start free Open in platform

Related vulnerabilities

Same products first, then exploited flaws of the same weakness class.

9.8CVE-2020-0646Microsoft .NET Framework input validation flaw enables remote code executionCVE-2020-0646 is a critical remote code execution vulnerability in the Microsoft .NET Framework caused by improper input validation, classified as XM…KEVEPSS 99%analysed7.8CVE-2020-1147Microsoft .NET Framework, SharePoint, and Visual Studio XML Deserialization RCEThe software fails to check the source markup of XML input, allowing crafted XML to trigger unsafe deserialization and remote code execution. It affe…KEVEPSS 94%analysed7.8CVE-2017-8759Microsoft .NET Framework remote code execution via malicious documentMicrosoft .NET Framework versions 2.0 through 4.7 contain a code injection flaw that lets an attacker run arbitrary code when a crafted document or a…KEVEPSS 89%analysed7.8CVE-2015-1671Microsoft DirectWrite TrueType Font Parsing Remote Code ExecutionThe Windows DirectWrite library fails to properly handle crafted TrueType fonts, allowing memory corruption that can lead to arbitrary code execution…KEVEPSS 49%analysed7.5CVE-2024-29059Microsoft .NET Framework error message information disclosureCVE-2024-29059 is an information disclosure flaw in Microsoft .NET Framework, classified as CWE-209 (error message information leak). A remote, unaut…KEVEPSS 99%analysed10.0CVE-2014-4073Microsoft .net framework permissions and access controls vulnerabilityMicrosoft .NET Framework 2.0 SP2, 3.5, 3.5.1, 4, 4.5, 4.5.1, and 4.5.2 processes unverified data during interaction with the ClickOnce installer, whi…EPSS 23%10.0CVE-2014-4121Microsoft .net framework vulnerabilityMicrosoft .NET Framework 2.0 SP2, 3.5, 3.5.1, 4, 4.5, 4.5.1, and 4.5.2 does not properly parse internationalized resource identifiers, which allows r…EPSS 19%10.0CVE-2014-1806Microsoft .net framework code injection vulnerabilityThe .NET Remoting implementation in Microsoft .NET Framework 1.1 SP1, 2.0 SP2, 3.5, 3.5.1, 4, 4.5, and 4.5.1 does not properly restrict memory access…EPSS 40%

Source: NIST National Vulnerability Database (record CVE-2013-3861), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.