CVE-2025-25003
Microsoft Visual Studio 2022 17.8.0 – 17.8.19
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2025-25003 is a high-severity Uncontrolled Search Path Element (CWE-427) vulnerability in Microsoft Visual Studio 2022. Its CVSS base score is 7.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to CM-6 (Configuration Settings) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-25003 is an uncontrolled search path element vulnerability (CWE-427) in Visual Studio. Published on 2025-03-11T17:16:38.043, it carries a CVSS v3.1 base score of 7.3 (AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H), indicating high potential impact from local exploitation.
A local attacker with low privileges (PR:L) can exploit this vulnerability with low attack complexity (AC:L), provided they induce user interaction (UI:R). Successful exploitation enables privilege escalation, resulting in high impacts to confidentiality, integrity, and availability (C:H/I:H/A:H) within the local scope (S:U).
The Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-25003 details mitigation strategies and available patches for addressing this issue.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-6345
Vulnerability Data
Uncontrolled search path element in Visual Studio allows an authorized attacker to elevate privileges locally.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 1 OS baseline
—
Mitigating Controls (NIST 800-53 r5) AI
Establishes restrictive configuration settings that can define and lock down approved search paths.
Enforces approved authorizations so that only intended actors can place or modify elements in the search path.
Limits privileges so unintended actors cannot write to or control directories in the product's search path.
Restricts logical and physical access to change system configuration, including search-path settings and directories.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices directly address design of search paths and resource loading.
Hardened configuration baselines can enforce safe search-path settings and reduce exposure.
Execution allow-listing can block malicious binaries placed in hijackable search locations.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect uncontrolled search-path issues but does not prevent them by itself.
Restricting software installation reduces the chance that an attacker-controlled path element is introduced into the search path.
Secure system architecture and engineering principles require explicit control over search paths and resource locations.
Secure coding practices directly address the use of fixed or controlled search paths that can be influenced by unintended actors.
Configuration management can enforce approved search-path settings but does not inherently prevent the weakness.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248577 OL 8 must enable kernel parameters to enforce Discretionary Access Control (DAC) on symlinks. prevents CWE-427