CVE-2022-29145 high CVSS 7.5

Vulnerability in Microsoft.AspNetCore.App.Runtime.win-x64 (CVE-2022-29145)

Summary

vulnerability in Microsoft.AspNetCore.App.Runtime.win-x64 (CVE-2022-29145). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 6.0.5 or later.

Original description

The description as published by the source.

.NET and Visual Studio Denial of Service Vulnerability

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A weakness called CVE-2022-29145 was discovered in Microsoft.
Severity is High (CVSS 7.5/10). If exploited, attackers can leak data or disrupt key functionality.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "Microsoft CVE-2022-29145".

CVE-2022-29145 (Microsoft). Severity: High / CVSSv3 7.5. Category: CWE-400.
Response plan:

Check the vendor advisory for affected versions and the patched release.
If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.

❓ What is the problem

A weakness (CVE-2022-29145) in Microsoft. A serious software flaw has been identified.

📍 Affected scope

Target versions of Microsoft (see vendor advisory). If running in production, identify exposure immediately.

🔥 Severity

Severity: High (CVSS 7.5/10). If exploited, attackers can leak data or disrupt key functionality.

🔧 How to fix

Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-400)

🛡️ Workaround

If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.

🔍 Detection

Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'Microsoft.AspNetCore.App.Runtime.win-x64' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Microsoft.AspNetCore.App.Runtime.win-x64 を grep し、稼働しているサービス・バージョンを把握する。
6
Apply patch patch
```
Upgrade Microsoft.AspNetCore.App.Runtime.win-x64 to 6.0.5
```
ステージング環境で 6.0.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。