Microsoft Windows Graphic Component Privilege Escalation
CVE-2023-21823 is a high-severity integer overflow or wraparound vulnerability in Microsoft Office for Android from Microsoft, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists version 16.0.16130.20156 as the first without the flaw, so updating Microsoft Office for Android to that release or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on February 14, 2023, which means attacks have been observed in the wild.
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Update Microsoft Office for Android to 16.0.16130.20156 or a later version.
- Update Microsoft Office for iOS to 2.70.23021003 or a later version.
- Update Microsoft Office for Universal to 16.0.14326.21330 or a later version.
- CISA's required action: Apply updates per vendor instructions.
- Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Microsoft | Microsoft Office for Android | 16.0.1 up to, but not including, 16.0.16130.20156 | 16.0.16130.20156 |
| Microsoft | Microsoft Office for iOS | 2.0.0 up to, but not including, 2.70.23021003 | 2.70.23021003 |
| Microsoft | Microsoft Office for Universal | 16.0.1 up to, but not including, 16.0.14326.21330 | 16.0.14326.21330 |
| Microsoft | Windows 10 Version 1507 | 10.0.10240.0 up to, but not including, 10.0.10240.19747 | 10.0.10240.19747 |
| Microsoft | Windows 10 Version 1607 | 10.0.14393.0 up to, but not including, 10.0.14393.5717 | 10.0.14393.5717 |
| Microsoft | Windows 10 Version 1809 | 10.0.17763.0 up to, but not including, 10.0.17763.4010; 10.0.0 up to, but not including, 10.0.17763.4010 | 10.0.17763.4010 |
| Microsoft | Windows 10 Version 20H2 | 10.0.0 up to, but not including, 10.0.19042.2604 | 10.0.19042.2604 |
| Microsoft | Windows 10 Version 21H2 | 10.0.19043.0 up to, but not including, 10.0.19044.2604 | 10.0.19044.2604 |
| Microsoft | Windows 10 Version 22H2 | 10.0.19045.0 up to, but not including, 10.0.19045.2604 | 10.0.19045.2604 |
| Microsoft | Windows 11 version 21H2 | 10.0.0 up to, but not including, 10.0.22621.1574 | 10.0.22621.1574 |
| Microsoft | Windows 11 version 22H2 | 10.0.22621.0 up to, but not including, 10.0.22621.1265 | 10.0.22621.1265 |
| Microsoft | Windows Server 2008 Service Pack 2 | 6.0.6003.0 up to, but not including, 6.0.6003.21915 | 6.0.6003.21915 |
| Microsoft | Windows Server 2008 R2 Service Pack 1 | 6.1.7601.0 up to, but not including, 6.1.7601.26366 | 6.1.7601.26366 |
| Microsoft | Windows Server 2008 R2 Service Pack 1 (Server Core installation) | 6.1.7601.0 up to, but not including, 6.1.7601.26366 | 6.1.7601.26366 |
| Microsoft | Windows Server 2008 Service Pack 2 (Server Core installation) | 6.0.6003.0 up to, but not including, 6.0.6003.21915 | 6.0.6003.21915 |
| Microsoft | Windows Server 2012 | 6.2.9200.0 up to, but not including, 6.2.9200.24116 | 6.2.9200.24116 |
| Microsoft | Windows Server 2012 (Server Core installation) | 6.2.9200.0 up to, but not including, 6.2.9200.24116 | 6.2.9200.24116 |
| Microsoft | Windows Server 2012 R2 | 6.3.9600.0 up to, but not including, 6.3.9600.20821 | 6.3.9600.20821 |
| Microsoft | Windows Server 2012 R2 (Server Core installation) | 6.3.9600.0 up to, but not including, 6.3.9600.20821 | 6.3.9600.20821 |
| Microsoft | Windows Server 2016 | 10.0.14393.0 up to, but not including, 10.0.14393.5717 | 10.0.14393.5717 |
| Microsoft | Windows Server 2016 (Server Core installation) | 10.0.14393.0 up to, but not including, 10.0.14393.5717 | 10.0.14393.5717 |
| Microsoft | Windows Server 2019 | 10.0.17763.0 up to, but not including, 10.0.17763.4010 | 10.0.17763.4010 |
| Microsoft | Windows Server 2019 (Server Core installation) | 10.0.17763.0 up to, but not including, 10.0.17763.4010 | 10.0.17763.4010 |
| Microsoft | Windows Server 2022 | 10.0.20348.0 up to, but not including, 10.0.20348.1547 | 10.0.20348.1547 |
| Microsoft | Windows 10 1507 | before 10.0.10240.19747 | 10.0.10240.19747 |
Version data comes from the organisation that assigned the CVE; 8 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
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- 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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (microsoft.com).
Official description
Windows Graphics Component Remote Code Execution Vulnerability
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Integer Overflow or Wraparound
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
How developers prevent this class of flaw
- Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. If possible, choose a language or compiler that performs automatic bounds checking.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Use libraries or frameworks that make it easier to handle numbers without unexpected consequences. Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++).
More Integer Overflow or Wraparound vulnerabilities (CWE-190)
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-21823US Government Resource
Recent Integer Overflow or Wraparound vulnerabilities
- 7.5 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 7.5 High severity
- 7.8 High severity
Spotted an error? Tell us.