# CVE-2024-6675: Deserialization of Untrusted Data Vulnerability in NI VeriStand Project File

> Attackers can achieve remote code execution by tricking users into opening a maliciously crafted project file in NI VeriStand.

- **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:** No
- **Published:** 22 Jul 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-24p4-6wf6-98xx

## What is CVE-2024-6675?

CVE-2024-6675 is a high-severity unsafe deserialization vulnerability in NI VeriStand, published on 22 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A deserialization of untrusted data vulnerability exists in NI VeriStand that may result in remote code execution.  Successful exploitation requires an attacker to get a user to open a specially crafted project file.  This vulnerability affects VeriStand 2024 Q2 and prior versions.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2024-6675?


## How do I fix CVE-2024-6675?

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

## Is CVE-2024-6675 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6675 and fix it if it is affected.

What it is: CVE-2024-6675 is a high-severity unsafe deserialization vulnerability in NI VeriStand, published on 22 Jul 2024. 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-2024-6675 in the wild and no public exploit code.

Affected product: NI VeriStand. 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-2024-6675/ (Markdown: https://insights.sbomify.com/CVE-2024-6675/index.md)
```

## Sources

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

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