# CVE-2022-25794: Memory corruption in Autodesk FBX Review

> Out-of-bounds read in Autodesk FBX Review allows code execution or information disclosure via malicious ActionScript Byte Code files.

- **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:** 11 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-779h-whfc-q2qp

## What is CVE-2022-25794?

CVE-2022-25794 is a high-severity memory corruption vulnerability in Autodesk FBX Review, published on 11 Apr 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

An Out-Of-Bounds Read Vulnerability in Autodesk FBX Review version 1.5.2 and prior may lead to code execution through maliciously crafted ActionScript Byte Code 'ABC' files or information disclosure. ABC files are created by the Flash compiler and contain executable code. This vulnerability in conjunction with other vulnerabilities could lead to code execution in the context of the current process.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Autodesk Fbx Review.

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

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

## Is CVE-2022-25794 being exploited?

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

## Other vulnerabilities in Autodesk FBX Review

- [CVE-2024-23139](https://insights.sbomify.com/CVE-2024-23139/): ActionScript Byte Code “ABC” Vulnerability in the Autodesk FBX Review software (high 7.8)
- [CVE-2021-27044](https://insights.sbomify.com/CVE-2021-27044/): Memory corruption in Autodesk FBX Review (high 7.8)
- [CVE-2021-40157](https://insights.sbomify.com/CVE-2021-40157/): Memory corruption in Autodesk FBX Review (high 7.8)
- [CVE-2021-27027](https://insights.sbomify.com/CVE-2021-27027/): Memory corruption in Autodesk FBX Review (high 7.8)
- [CVE-2021-27028](https://insights.sbomify.com/CVE-2021-27028/): Memory corruption in Autodesk FBX Review (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-25794 is a high-severity memory corruption vulnerability in Autodesk FBX Review, published on 11 Apr 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-25794 in the wild and no public exploit code.

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

## Sources

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

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