Microsoft Windows Shell Remote Code Execution
CVE-2018-8414 is a high-severity improper input validation vulnerability in Windows 10 Servers from Microsoft, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. Affected Windows 10 Servers versions: version 1709 (Server Core Installation); version 1803 (Server Core Installation). The record does not name a fixed version, so check the vendor advisory. CISA added it to the Known Exploited Vulnerabilities catalogue on March 25, 2022, which means attacks have been observed in the wild.
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Check which version of Windows 10 Servers you run against the affected versions below, and install the vendor's latest release.
- CISA's required action: Apply updates per vendor instructions.
- Read the advisory on portal.msrc.microsoft.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Microsoft | Windows 10 Servers | version 1709 (Server Core Installation); version 1803 (Server Core Installation) | Not stated |
| Microsoft | Windows 10 | Version 1703 for 32-bit Systems; Version 1703 for x64-based Systems; Version 1709 for 32-bit Systems; Version 1709 for x64-based Systems; Version 1803 for 32-bit Systems; Version 1803 for x64-based Systems | Not stated |
| Microsoft | Windows 10 1703 | Not specified in the record | Not stated |
| Microsoft | Windows 10 1709 | Not specified in the record | Not stated |
| Microsoft | Windows 10 1803 | Not specified in the record | Not stated |
| Microsoft | Windows Server 1709 | Not specified in the record | Not stated |
| Microsoft | Windows Server 1803 | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.8 | High | NVD |
| CVSS 3.1 | 8.8 | High | CISA (ADP) |
| CVSS 2.0 | 9.3 | High | NVD |
Official description
A remote code execution vulnerability exists when the Windows Shell does not properly validate file paths, aka "Windows Shell Remote Code Execution Vulnerability." This affects Windows 10 Servers, Windows 10.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Input Validation
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
How developers prevent this class of flaw
- Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
- Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
- Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.
Timeline
- CVE record published.
- Added to CISA's Known Exploited Vulnerabilities catalogue.
- Deadline for US federal agencies to remediate, set by CISA.
- CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2018-8414US Government Resource
Other vulnerabilities in Windows 10 Servers
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Microsoft Win32k Privilege Escalation Exploited
- 7.8 High severity
Microsoft Windows Privilege Escalation Exploited
- 7.8 High severity
- 7.8 High severity
Recent Improper Input Validation vulnerabilities
- 9.8 Critical severity
Drupal Core Remote Code Execution Exploited
- 8.6 High severity
- 8.6 High severity
- 7.5 High severity
- 7.5 High severity
- 5.9 Medium severity
Spotted an error? Tell us.