LiveActive security incident?Get immediate response
CVE Record

CVE-2023-38180: .NET and Visual Studio Denial of Service Vulnerability

.NET and Visual Studio Denial of Service Vulnerability

HighCVSS 7.5Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-38180 can let a remote, unauthenticated attacker exhaust resources in affected Microsoft .NET, ASP.NET Core, or Visual Studio software, disrupting availability. It does not indicate data theft or modification. CISA KEV inclusion means exploitation has been observed, so reachable production services deserve urgent attention.

Executive priority

Treat as an urgent availability risk. Assign immediate ownership, identify exposed production workloads, and apply vendor updates promptly. Prioritize critical customer-facing or operational services because successful exploitation may cause outages, even though the supplied evidence indicates no direct confidentiality or integrity impact.

Technical view

This is a CWE-400 resource-consumption denial-of-service vulnerability with CVSS 3.1 score 7.5. The supplied vector indicates network access, low complexity, no privileges, no user interaction, and high availability impact without confidentiality or integrity impact. Microsoft identifies affected .NET 6.0, .NET 7.0, ASP.NET Core, and Visual Studio 2022 releases.

Likely exposure

Risk is highest for network-reachable services using affected .NET or ASP.NET Core components because the attack requires neither authentication nor user interaction. Visual Studio installations listed in the bundle also require review. The supplied affected-version data may not describe complete ranges, so confirm exact exposure against Microsoft's advisory.

Exploitation context

The source bundle marks this CVE as present in CISA's Known Exploited Vulnerabilities catalog, supporting active exploitation. It also reports exploit maturity as proof-of-concept. No campaign details, indicators, attack scale, or affected deployment patterns are provided, so broader exploitation characteristics remain unknown.

Researcher notes

The bundle identifies CWE-400 and a remotely reachable, unauthenticated denial-of-service condition. It does not describe the malformed input, vulnerable code path, indicators, or fixed version numbers. The ASP.NET Core entry pairs product 2.1 with version 2.0, an apparent inconsistency requiring confirmation against Microsoft's authoritative affected-product matrix.

Mitigation direction

  • Apply the applicable Microsoft security updates identified in the vendor advisory.
  • Prioritize network-reachable production services using affected .NET or ASP.NET Core components.
  • Update affected Visual Studio 2022 installations through supported Microsoft servicing channels.
  • Where immediate updating is impossible, reduce untrusted network reachability and monitor resource exhaustion.
  • Check Microsoft guidance for any product-specific mitigations or revised affected-version information.

Validation and detection

  • Inventory deployed .NET, ASP.NET Core, and Visual Studio versions across servers and developer systems.
  • Compare installed versions and update levels with Microsoft's CVE advisory.
  • Confirm security updates installed successfully and restart components where vendor guidance requires it.
  • Test exposed services for normal availability and stable resource consumption after remediation.
  • Review monitoring data for unexplained CPU, memory, connection, or service-availability spikes.
Prepared
Confidence
high
Sources
4

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-400: 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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-38180 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
5Timeline events
2ADP providers
5Source links

CISA KEV status

Status
Known exploited
Source
CISA-ADP
Date added
KEV reference

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: activeAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O/RC:C3.93.6microsoft

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2023-38180Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. Added to KEVCISA-ADP

    CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.

  4. ADP timelineCISA-ADP

    CVE-2023-38180 added to CISA KEV

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvcother:kev
  • 2023-08-09T00:00:00.000Z: CVE-2023-38180 added to CISA KEV
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Microsoft.NET 6.06.0.0Listed
Microsoft.NET 7.07.0.0Listed
MicrosoftASP.NET Core 2.12.0Listed
MicrosoftMicrosoft Visual Studio 2022 version 17.217.2.0Listed
MicrosoftMicrosoft Visual Studio 2022 version 17.417.4.0Listed
MicrosoftMicrosoft Visual Studio 2022 version 17.617.6.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.