# CVE-2018-1000618: Denial of service in n/a

> A stack overflow in the ABI serializer allows remote attackers to crash EOSIO network nodes via crafted network requests.

- **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:** 9 Jul 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-5frv-4h27-cphv

## What is CVE-2018-1000618?

CVE-2018-1000618 is a critical denial of service vulnerability in n/a, published on 9 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

EOSIO/eos eos version after commit f1545dd0ae2b77580c2236fdb70ae7138d2c7168 contains a stack overflow vulnerability in abi_serializer that can result in attack eos network node. This attack appear to be exploitable via network request. This vulnerability appears to have been fixed in after commit cf7209e703e6d3f7a5413e0cb1fe88a4d8e4b38d .

Weakness: CWE-674 (Uncontrolled Recursion)

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

It affects 1 product.


Products: Eosio Project Eos.

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

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

## Is CVE-2018-1000618 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-26300](https://insights.sbomify.com/CVE-2022-26300/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1000618 is a critical denial of service vulnerability in n/a, published on 9 Jul 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-1000618 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-1000618/ (Markdown: https://insights.sbomify.com/CVE-2018-1000618/index.md)
```

## Sources

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

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