Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2020-15801 critical CVSS 9.8

Vulnerability in Microsoft Windows (CVE-2020-15801)

Summary

Vulnerability in Microsoft Windows (CVE-2020-15801). Successful exploitation can lead to full system takeover.

Original description

The description as published by the source.

In Python 3.8.4, sys.path restrictions specified in a python38._pth file are ignored, allowing code to be loaded from arbitrary locations. The ._pth file (e.g., the python._pth file) is not affected.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

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 vulnerability tracked as CVE-2020-15801 has been found in Microsoft Windows.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Microsoft Windows CVE-2020-15801" on the vendor's site.

CVE-2020-15801 (Microsoft Windows) — CWE-426 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-426) exists in Microsoft Windows.

📍 Affected scope

Check the vendor advisory for the affected versions of Microsoft Windows.

🔥 Severity

Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Windows' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

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

  1. 1
    Identify exposure identify 
    grep -r 'Windows' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Windows を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Bitnami libpython
[{"type":"SEMVER","events":[{"introduced":"3.7.0"},{"fixed":"3.7.9"},{"introduced":"3.8.0"},{"fixed":"3.8.5"}]}]
Bitnami python-min
[{"type":"SEMVER","events":[{"introduced":"3.7.0"},{"fixed":"3.7.9"},{"introduced":"3.8.0"},{"fixed":"3.8.5"}]}]
Bitnami python
[{"type":"SEMVER","events":[{"introduced":"3.7.0"},{"fixed":"3.7.9"},{"introduced":"3.8.0"},{"fixed":"3.8.5"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details