CVE-2022-21911 json
.NET Framework Denial of Service Vulnerability
published 2022-01-11 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-27067
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.2%
- EPSS 3.2% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
.NET Framework Denial of Service Vulnerability
Patch / fix
- Microsoft Microsoft .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1/4.7.2 4.7.3905.0
- Microsoft Microsoft .NET Framework 3.5 AND 4.8 4.8.4465.0
- Microsoft Microsoft .NET Framework 4.8 4.8.4465.0
- Microsoft Microsoft .NET Framework 3.5 AND 4.7.2 4.7.3905.0
- Microsoft Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 10.0.14393.4886
- Microsoft Microsoft .NET Framework 2.0 Service Pack 2 2.0.50727.8955
- Microsoft Microsoft .NET Framework 4.6 4.7.3905.0
- Microsoft Microsoft .NET Framework 3.5 2.0.50727.8955
- Microsoft Microsoft .NET Framework 3.5.1 2.0.50727.8955
- Microsoft Microsoft .NET Framework 4.5.2 4.0.30319.36720
Exploit prediction
3.23% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Affected products
- Microsoft Microsoft .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1/4.7.2
- Microsoft Microsoft .NET Framework 3.5 AND 4.8
- Microsoft Microsoft .NET Framework 4.8
- Microsoft Microsoft .NET Framework 3.5 AND 4.7.2
- Microsoft Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2
- Microsoft Microsoft .NET Framework 2.0 Service Pack 2
- Microsoft Microsoft .NET Framework 4.6
- Microsoft Microsoft .NET Framework 3.5
- Microsoft Microsoft .NET Framework 3.5.1
- Microsoft Microsoft .NET Framework 4.5.2
References
Sources
- CVE List CVE-2022-21911
- NVD CVE-2022-21911
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.