cve.bz

CVE-2023-36394 microsoft: Link Following

7.0 highEPSS 6.6%Fix available

High (7.0) in microsoft. EPSS 6.6% estimated probability of exploitation activity in the next 30 days.

On this page
Windows Search Service Elevation of Privilege Vulnerability

Severity

CVSS 3.1

7.0 high
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
6.6% (unchanged from 6.6% a week ago; 6.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 94th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2024-03-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-59 Improper Link Resolution Before File Access (Link Following)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-36394 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-36394?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-36394?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-36394 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Windows 10 Version 1809from 10.0.17763.0 before 10.0.17763.5122
Microsoft Windows 10 Version 1809from 10.0.0 before 10.0.17763.5122
Microsoft Windows Server 2019from 10.0.17763.0 before 10.0.17763.5122
Microsoft Windows Server 2019 (Server Core installation)from 10.0.17763.0 before 10.0.17763.5122
Microsoft Windows Server 2022from 10.0.20348.0 before 10.0.20348.2113
Microsoft Windows 11 version 21H2from 10.0.0 before 10.0.22000.2600
Microsoft Windows 10 Version 21H2from 10.0.19043.0 before 10.0.19043.3693
Microsoft Windows 10 Version 22H2from 10.0.19045.0 before 10.0.19045.3693
Microsoft Windows 10 Version 1507from 10.0.10240.0 before 10.0.10240.20308
Microsoft Windows 10 Version 1607from 10.0.14393.0 before 10.0.14393.6452
Microsoft Windows Server 2016from 10.0.14393.0 before 10.0.14393.6452
Microsoft Windows Server 2016 (Server Core installation)from 10.0.14393.0 before 10.0.14393.6452

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON