# CVE-2022-47024: Null dereference in n/a

> A null pointer dereference in Vim's X11 GUI allows attackers to cause a denial of service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** Yes
- **Published:** 20 Jan 2023
- **Updated:** 3 Apr 2025
- **Also known as:** ALPINE-CVE-2022-47024, ALSA-2023:0958, BELL-CVE-2022-47024, CLSA-2023-1680210210, DEBIAN-CVE-2022-47024, GHSA-5jpw-hxh6-542f, RHSA-2023:0958, RLSA-2023:0958, UBUNTU-CVE-2022-47024

## What is CVE-2022-47024?

CVE-2022-47024 is a high-severity vulnerability in Vim Vim, published on 20 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A null pointer dereference issue was discovered in function gui_x11_create_blank_mouse in gui_x11.c in vim 8.1.2269 thru 9.0.0339 allows attackers to cause denial of service or other unspecified impacts.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2022-47024?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vim-X11` | AlmaLinux:9 | All versions | 2:8.2.2637-20.el9_1 |
| `vim-common` | AlmaLinux:9 | All versions | 2:8.2.2637-20.el9_1 |
| `vim-enhanced` | AlmaLinux:9 | All versions | 2:8.2.2637-20.el9_1 |
| `vim-filesystem` | AlmaLinux:9 | All versions | 2:8.2.2637-20.el9_1 |
| `vim-minimal` | AlmaLinux:9 | All versions | 2:8.2.2637-20.el9_1 |
| `vim-X11` | Red Hat:enterprise_linux:9::appstream | All versions | 2:8.2.2637-20.el9_1 |
| `vim-X11-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 2:8.2.2637-20.el9_1 |
| `vim-common` | Red Hat:enterprise_linux:9::appstream | All versions | 2:8.2.2637-20.el9_1 |
| `vim-common-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 2:8.2.2637-20.el9_1 |
| `vim-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 2:8.2.2637-20.el9_1 |
| `vim-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 2:8.2.2637-20.el9_1 |
| `vim-enhanced` | Red Hat:enterprise_linux:9::appstream | All versions | 2:8.2.2637-20.el9_1 |
| `vim-enhanced-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 2:8.2.2637-20.el9_1 |
| `vim-minimal-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 2:8.2.2637-20.el9_1 |
| `vim` | Red Hat:enterprise_linux:9::baseos | All versions | 2:8.2.2637-20.el9_1 |
| `vim-X11-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 2:8.2.2637-20.el9_1 |
| `vim-common-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 2:8.2.2637-20.el9_1 |
| `vim-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 2:8.2.2637-20.el9_1 |
| `vim-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 2:8.2.2637-20.el9_1 |
| `vim-enhanced-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 2:8.2.2637-20.el9_1 |
| `vim-filesystem` | Red Hat:enterprise_linux:9::baseos | All versions | 2:8.2.2637-20.el9_1 |
| `vim-minimal` | Red Hat:enterprise_linux:9::baseos | All versions | 2:8.2.2637-20.el9_1 |
| `vim-minimal-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 2:8.2.2637-20.el9_1 |
| `vim` | Rocky Linux:9 | All versions | 2:8.2.2637-20.el9_1 |

Products: Vim Vim.

## How do I fix CVE-2022-47024?

Apply the vendor's patch.

## Is CVE-2022-47024 being exploited?

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

## Other vulnerabilities in Vim Vim

- [CVE-2020-20703](https://insights.sbomify.com/CVE-2020-20703/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-6349](https://insights.sbomify.com/CVE-2017-6349/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-6350](https://insights.sbomify.com/CVE-2017-6350/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-5953](https://insights.sbomify.com/CVE-2017-5953/): Integer overflow in n/a (critical 9.8)
- [CVE-2008-3075](https://insights.sbomify.com/CVE-2008-3075/): Command injection in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-47024 and fix it if it is affected.

What it is: CVE-2022-47024 is a high-severity vulnerability in Vim Vim, published on 20 Jan 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-2022-47024 in the wild and no public exploit code.

Affected product: Vim Vim. 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-2022-47024/ (Markdown: https://insights.sbomify.com/CVE-2022-47024/index.md)
```

## Sources

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

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