Cyber Resilience

CVE-2022-23267

High

Published: 10 May 2022

Published
10 May 2022
Modified
02 January 2025
KEV Added
Patch
CVSS Score v3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0642 91.3th percentile
Risk Priority 19 60% EPSS · 20% KEV · 20% CVSS

Summary

CVE-2022-23267 is a high-severity an unspecified weakness vulnerability in Fedoraproject Fedora. Its CVSS base score is 7.5 (High).

Operationally, ranked in the top 8.7% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

Deeper analysis

CVE-2022-23267 is a denial-of-service vulnerability affecting .NET and Visual Studio. It received a CVSS 3.1 base score of 7.5, reflecting a network-accessible flaw that requires no authentication or user interaction and produces a high impact on availability while leaving confidentiality and integrity untouched.

An unauthenticated remote attacker can send specially crafted requests or inputs to trigger the flaw, causing the affected .NET or Visual Studio component to become unresponsive or crash and thereby denying service to legitimate users.

Microsoft security advisories published at the listed MSRC URLs describe the issue and direct administrators to apply the patches released in the May 2022 update cycle; several Fedora mailing-list announcements also reference coordinated package updates for downstream distributions.

The associated EPSS score rose from a low baseline to a recorded peak of 0.0819 before settling at the current value of 0.0642, indicating a modest post-disclosure increase in observed exploitation interest.

EU & UK References

Vulnerability details

.NET and Visual Studio Denial of Service Vulnerability

CWE(s)

Related Threats

No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.

Affected Assets

microsoft
.net
5.0, 6.0.0
microsoft
.net core
3.1
microsoft
powershell
7.0 — 7.0.11 · 7.2 — 7.2.4
microsoft
visual studio 2019
16.0 — 16.9.21 · 16.10 — 16.11.14
microsoft
visual studio 2022
17.0, 17.1
fedoraproject
fedora
34, 35, 36

Mitigating Controls

No mitigating controls mapped yet. The per-CVE control annotator has not reached this CVE.

References