# CVE-2023-24910: Windows Graphics Component Elevation of Privilege Vulnerability

> A null pointer dereference in the Windows Graphics Component allows attackers to escalate privileges on affected systems.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Mar 2023
- **Updated:** 1 Jan 2025
- **Also known as:** GHSA-pvgx-cgc8-6g74

## What is CVE-2023-24910?

CVE-2023-24910 is a high-severity vulnerability in Microsoft Office, published on 14 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Windows Graphics Component Elevation of Privilege Vulnerability

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2023-24910?

It affects 15 products.


Products: Microsoft 365, Microsoft Office, Microsoft Office Long Term Servicing Channel, Microsoft Windows 10 1607, Microsoft Windows 10 1809, Microsoft Windows 10 20h2, Microsoft Windows 10 21h2, Microsoft Windows 10 22h2, Microsoft Windows 11 21h2, Microsoft Windows 11 22h2, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022.

## How do I fix CVE-2023-24910?

No fix has been published for CVE-2023-24910 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-24910 being exploited?

There is no known exploitation of CVE-2023-24910 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-24910 and fix it if it is affected.

What it is: CVE-2023-24910 is a high-severity vulnerability in Microsoft Office, published on 14 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-24910 in the wild and no public exploit code.

Affected product: Microsoft Office. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-24910/ (Markdown: https://insights.sbomify.com/CVE-2023-24910/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-24910
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-24910
- OSV: https://osv.dev/vulnerability/CVE-2023-24910

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-24910/
Summaries are generated and may contain mistakes; the official description above is the record.