# CVE-2020-10599: Memory corruption in VBASE Editor

> A buffer overflow in VISAM VBASE Editor's ActiveX component allows attackers to execute arbitrary code or cause denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q998-jx47-mggq

## What is CVE-2020-10599?

CVE-2020-10599 is a critical memory corruption vulnerability in VISAM VBASE Editor, published on 3 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

VISAM VBASE Editor version 11.5.0.2 and VBASE Web-Remote Module may allow a vulnerable ActiveX component to be exploited resulting in a buffer overflow, which may lead to a denial-of-service condition and execution of arbitrary code.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2020-10599?

It affects 2 products.


Products: Visam Vbase Editor, Visam Vbase Web-Remote.

## How do I fix CVE-2020-10599?

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

## Is CVE-2020-10599 being exploited?

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

## Other vulnerabilities in VISAM VBASE Editor

- [CVE-2020-7004](https://insights.sbomify.com/CVE-2020-7004/): Misconfiguration in VBASE Editor (high 8.8)
- [CVE-2020-10601](https://insights.sbomify.com/CVE-2020-10601/): Weak cryptography in VBASE Editor (high 7.8)
- [CVE-2020-7000](https://insights.sbomify.com/CVE-2020-7000/): Information disclosure in VBASE Editor (high 7.5)
- [CVE-2020-7008](https://insights.sbomify.com/CVE-2020-7008/): Path traversal in VBASE Editor (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-10599 and fix it if it is affected.

What it is: CVE-2020-10599 is a critical memory corruption vulnerability in VISAM VBASE Editor, published on 3 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-10599 in the wild and no public exploit code.

Affected product: VISAM VBASE Editor. 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-2020-10599/ (Markdown: https://insights.sbomify.com/CVE-2020-10599/index.md)
```

## Sources

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

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