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

> Remote attackers can cause denial of service in Emercoin nodes by sending invalid headers or blocks, exhausting disk and RAM resources.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 5 Nov 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h626-57vg-4vmq

## What is CVE-2018-19152?

CVE-2018-19152 is a high-severity denial of service vulnerability in n/a, published on 5 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

emercoin through 0.7 (a chain-based proof-of-stake cryptocurrency) allows a remote denial of service. The attacker sends invalid headers/blocks. The attack requires no stake and can fill the victim's disk and RAM.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Emercoin Emercoin.

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

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

## Is CVE-2018-19152 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-19152 is a high-severity denial of service vulnerability in n/a, published on 5 Nov 2019. 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-19152 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-19152/ (Markdown: https://insights.sbomify.com/CVE-2018-19152/index.md)
```

## Sources

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

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