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

> Remote attackers with minimal stake can cause denial of service in Phore cryptocurrency nodes by sending invalid headers that fill victim disk space.

- **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-w3vw-x68c-hm6v

## What is CVE-2018-19157?

CVE-2018-19157 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

Phore through 1.3.3.1 (a chain-based proof-of-stake cryptocurrency) allows a remote denial of service, exploitable by an attacker who acquires even a small amount of stake/coins in the system. The attacker sends invalid headers/blocks, which are stored on the victim's disk.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Phore Phore.

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

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

## Is CVE-2018-19157 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-19157 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-19157 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-19157/ (Markdown: https://insights.sbomify.com/CVE-2018-19157/index.md)
```

## Sources

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

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