# CVE-2018-17569: Integer overflow in n/a

> An integer overflow in ViaBTC Exchange Server leads to memory corruption, potentially allowing attackers to execute code or cause denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 26 Sep 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4x8q-mqx2-hxx9

## What is CVE-2018-17569?

CVE-2018-17569 is a critical vulnerability in n/a, published on 26 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

network/nw_buf.c in ViaBTC Exchange Server before 2018-08-21 has an integer overflow leading to memory corruption.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Viabtc Viabtc Exchange Server.

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

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

## Is CVE-2018-17569 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-17568](https://insights.sbomify.com/CVE-2018-17568/): Integer overflow in n/a (critical 9.8)
- [CVE-2018-17570](https://insights.sbomify.com/CVE-2018-17570/): Integer overflow in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-17569 is a critical vulnerability in n/a, published on 26 Sep 2018. 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-2018-17569 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-17569/ (Markdown: https://insights.sbomify.com/CVE-2018-17569/index.md)
```

## Sources

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

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