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

> Attackers can cause a denial of service in Bro network monitors by sending malicious IRC protocol names commands.

- **Severity:** High 7.5 (`CVSS:3.0/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:** 13 Sep 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-fcrf-wj6f-p332, UBUNTU-CVE-2018-17019

## What is CVE-2018-17019?

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

### Official description

In Bro through 2.5.5, there is a DoS in IRC protocol names command parsing in analyzer/protocol/irc/IRC.cc.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Bro Bro.

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

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

## Is CVE-2018-17019 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-1000458](https://insights.sbomify.com/CVE-2017-1000458/): Memory corruption in n/a (critical 9.8)
- [CVE-2018-16807](https://insights.sbomify.com/CVE-2018-16807/): Denial of service in n/a (high 7.5)
- [CVE-2015-1521](https://insights.sbomify.com/CVE-2015-1521/): Memory corruption in n/a (high 7.5)
- [CVE-2015-1522](https://insights.sbomify.com/CVE-2015-1522/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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