CVE-2023-36563Exploited in the wildNVD status: Analyzed
Microsoft WordPad Information Disclosure
CVE-2023-36563 is a medium-severity improper input validation vulnerability in Windows 10 Version 1809 from Microsoft, with a CVSS 3.1 base score of 5.5 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version 10.0.17763.4974 as the first without the flaw, so updating Windows 10 Version 1809 to that release or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on October 10, 2023, which means attacks have been observed in the wild.
Patch now
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Update Windows 10 Version 1809 to 10.0.17763.4974 or a later version.
- Update Windows Server 2019 to 10.0.17763.4974 or a later version.
- Update Windows Server 2019 (Server Core installation) to 10.0.17763.4974 or a later version.
- CISA's required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
- Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.
- 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 Version 1809 | 10.0.17763.0 up to, but not including, 10.0.17763.4974; 10.0.0 up to, but not including, 10.0.17763.4974 | 10.0.17763.4974 |
| Microsoft | Windows Server 2019 | 10.0.17763.0 up to, but not including, 10.0.17763.4974 | 10.0.17763.4974 |
| Microsoft | Windows Server 2019 (Server Core installation) | 10.0.17763.0 up to, but not including, 10.0.17763.4974 | 10.0.17763.4974 |
| Microsoft | Windows Server 2022 | 10.0.20348.0 up to, but not including, 10.0.20348.2031 | 10.0.20348.2031 |
| Microsoft | Windows 11 version 21H2 | 10.0.0 up to, but not including, 10.0.22000.2538 | 10.0.22000.2538 |
| Microsoft | Windows 10 Version 21H2 | 10.0.19043.0 up to, but not including, 10.0.19041.3570 | 10.0.19041.3570 |
| Microsoft | Windows 11 version 22H2 | 10.0.22621.0 up to, but not including, 10.0.22621.2428 | 10.0.22621.2428 |
| Microsoft | Windows 10 Version 22H2 | 10.0.19045.0 up to, but not including, 10.0.19045.3570 | 10.0.19045.3570 |
| Microsoft | Windows 10 Version 1507 | 10.0.10240.0 up to, but not including, 10.0.10240.20232 | 10.0.10240.20232 |
| Microsoft | Windows 10 Version 1607 | 10.0.14393.0 up to, but not including, 10.0.14393.6351 | 10.0.14393.6351 |
| Microsoft | Windows Server 2016 | 10.0.14393.0 up to, but not including, 10.0.14393.6351 | 10.0.14393.6351 |
| Microsoft | Windows Server 2016 (Server Core installation) | 10.0.14393.0 up to, but not including, 10.0.14393.6351 | 10.0.14393.6351 |
| Microsoft | Windows Server 2008 Service Pack 2 | 6.0.6003.0 up to, but not including, 6.0.6003.22317 | 6.0.6003.22317 |
| Microsoft | Windows Server 2008 Service Pack 2 (Server Core installation) | 6.0.6003.0 up to, but not including, 6.0.6003.22317 | 6.0.6003.22317 |
| Microsoft | Windows Server 2008 R2 Service Pack 1 | 6.1.7601.0 up to, but not including, 6.1.7601.26769 | 6.1.7601.26769 |
| Microsoft | Windows Server 2008 R2 Service Pack 1 (Server Core installation) | 6.1.7601.0 up to, but not including, 6.1.7601.26769 | 6.1.7601.26769 |
| Microsoft | Windows Server 2012 | 6.2.9200.0 up to, but not including, 6.2.9200.24523 | 6.2.9200.24523 |
| Microsoft | Windows Server 2012 (Server Core installation) | 6.2.9200.0 up to, but not including, 6.2.9200.24523 | 6.2.9200.24523 |
| Microsoft | Windows Server 2012 R2 | 6.3.9600.0 up to, but not including, 6.3.9600.21620 | 6.3.9600.21620 |
| Microsoft | Windows Server 2012 R2 (Server Core installation) | 6.3.9600.0 up to, but not including, 6.3.9600.21620 | 6.3.9600.21620 |
| Microsoft | Windows 10 1507 | before 10.0.10240.20232 | 10.0.10240.20232 |
| Microsoft | Windows 10 1607 | before 10.0.14393.6351 | 10.0.14393.6351 |
| Microsoft | Windows 10 1809 | before 10.0.17763.4974 | 10.0.17763.4974 |
| Microsoft | Windows 10 21h2 | before 10.0.19041.3570 | 10.0.19041.3570 |
| Microsoft | Windows 10 22h2 | before 10.0.19045.3570 | 10.0.19045.3570 |
Version data comes from the organisation that assigned the CVE; 3 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- 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
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 6.5 | Medium | CNA (microsoft.com) |
| CVSS 3.1 | 5.5 | Medium | NVD |
Official description
Microsoft WordPad Information Disclosure Vulnerability
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-2023-36563US Government Resource
Recent Improper Input Validation vulnerabilities
- 9.8 Critical severity
- 7.8 High severity
- 8.1 High severity
- 8.2 High severity
- 9.1 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.