# GHSA-f7r3-p866-q9qr: ircdkit vulnerable to Denial of Service due to unhandled connection end event

> Remote attackers can cause a denial of service in applications using the ircdkit library by triggering an unhandled connection end event.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Jun 2019

## What is GHSA-f7r3-p866-q9qr?

GHSA-f7r3-p866-q9qr is a denial of service vulnerability in ircdkit, published on 3 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Versions of `ircdkit` 1.0.3 and prior are vulnerable to a remote denial of service.

## Recommendation

Upgrade to version 1.0.4.

## Which versions are affected by GHSA-f7r3-p866-q9qr?

2 open source packages ship an affected version, including ircdkit.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ircdkit` | npm | All versions | 1.0.4 |
| `ircdkit` | npm | All versions | 1.0.4 |

## How do I fix GHSA-f7r3-p866-q9qr?

Upgrade ircdkit to 1.0.4 or later.

## Is GHSA-f7r3-p866-q9qr being exploited?

There is no known exploitation of GHSA-f7r3-p866-q9qr in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-f7r3-p866-q9qr and fix it if it is affected.

What it is: GHSA-f7r3-p866-q9qr is a denial of service vulnerability in ircdkit, published on 3 Jun 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 GHSA-f7r3-p866-q9qr in the wild and no public exploit code.

Affected packages and fixed versions:
- ircdkit (npm): affected all versions; fixed in 1.0.4
- ircdkit (npm): affected all versions; fixed in 1.0.4

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/GHSA-f7r3-p866-q9qr/ (Markdown: https://insights.sbomify.com/GHSA-f7r3-p866-q9qr/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-f7r3-p866-q9qr

---
From sbomify Insights: https://insights.sbomify.com/GHSA-f7r3-p866-q9qr/
Summaries are generated and may contain mistakes; the official description above is the record.