# CVE-2023-45920: Null dereference in n/a

> A NULL pointer dereference in Xfig can cause a denial of service when interacting with anomalous X server behavior.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Mar 2024
- **Updated:** 4 Nov 2025
- **Also known as:** DEBIAN-CVE-2023-45920, GHSA-57m4-vwwv-mmqr, MGASA-2024-0125, SUSE-SU-2024:1196-1

## What is CVE-2023-45920?

CVE-2023-45920 is a medium-severity vulnerability in n/a, published on 27 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Xfig v3.2.8 was discovered to contain a NULL pointer dereference when calling XGetWMHints(). NOTE: this is disputed because it is not expected that an X application should continue to run when there is arbitrary anomalous behavior from the X server or window manager.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `xfig` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 3.2.8a-4.6.1 |

Products: Xfig Project Xfig.

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

Apply the vendor's patch.

## Is CVE-2023-45920 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-40241](https://insights.sbomify.com/CVE-2021-40241/): Memory corruption in n/a (critical 9.8)
- [CVE-2019-19555](https://insights.sbomify.com/CVE-2019-19555/): Memory corruption in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-45920 is a medium-severity vulnerability in n/a, published on 27 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-45920 in the wild and no public exploit code.

Affected product: n/a. 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-45920/ (Markdown: https://insights.sbomify.com/CVE-2023-45920/index.md)
```

## Sources

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

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