# CVE-2022-27872: Null dereference in Navisworks

> A malicious PDF file can trigger a null pointer dereference in Autodesk Navisworks, allowing attackers to execute arbitrary code, read sensitive data, or cause a crash.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-vqp7-jhj6-766w

## What is CVE-2022-27872?

CVE-2022-27872 is a high-severity vulnerability in Navisworks, published on 21 Jun 2022. 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

A maliciously crafted PDF file may be used to dereference a pointer for read or write operation while parsing PDF files in Autodesk Navisworks 2022. The vulnerability exists because the application fails to handle a crafted PDF file, which causes an unhandled exception. An attacker can leverage this vulnerability to cause a crash or read sensitive data or execute arbitrary code.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions)

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

It affects 1 product.


Products: Autodesk Navisworks.

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

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

## Is CVE-2022-27872 being exploited?

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

## Other vulnerabilities in Navisworks

- [CVE-2025-1658](https://insights.sbomify.com/CVE-2025-1658/): DWFX File Parsing Out-of-Bounds Read Vulnerability (high 7.8)
- [CVE-2025-1659](https://insights.sbomify.com/CVE-2025-1659/): DWFX File Parsing Out-of-Bounds Read Vulnerability (high 7.8)
- [CVE-2025-1660](https://insights.sbomify.com/CVE-2025-1660/): DWFX File Parsing Memory Corruption Vulnerability (high 7.8)
- [CVE-2024-11422](https://insights.sbomify.com/CVE-2024-11422/): DWFX File Parsing Vulnerabilities in Autodesk Navisworks Desktop Software (high 7.8)
- [CVE-2024-12178](https://insights.sbomify.com/CVE-2024-12178/): DWFX File Parsing Vulnerabilities in Autodesk Navisworks Desktop Software (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-27872 is a high-severity vulnerability in Navisworks, published on 21 Jun 2022. 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-2022-27872 in the wild and no public exploit code.

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

## Sources

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

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