# CVE-2018-18987: Deserialization in n/a

> VT-Designer fails to validate user-supplied input from files, allowing attackers to write to memory and potentially execute code or crash the application.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-25p3-j54h-933p

## What is CVE-2018-18987?

CVE-2018-18987 is a high-severity unsafe deserialization vulnerability in n/a, published on 30 Nov 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

VT-Designer Version 2.1.7.31 is vulnerable by the program populating objects with user supplied input via a file without first checking for validity, allowing attacker supplied input to be written to known memory locations. This may cause the program to crash or allow remote code execution.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2018-18987?

It affects 1 product.


Products: Invt Vt-Designer.

## How do I fix CVE-2018-18987?

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

## Is CVE-2018-18987 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-18983](https://insights.sbomify.com/CVE-2018-18983/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-18987 and fix it if it is affected.

What it is: CVE-2018-18987 is a high-severity unsafe deserialization vulnerability in n/a, published on 30 Nov 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-18987 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-2018-18987/ (Markdown: https://insights.sbomify.com/CVE-2018-18987/index.md)
```

## Sources

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

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