# CVE-2017-15227: Use after free in n/a

> A use-after-free vulnerability in Irssi allows attackers to cause denial of service or potentially execute code via channel synchronization issues.

- **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:** Yes
- **Published:** 22 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-15227, DEBIAN-CVE-2017-15227, GHSA-fxx4-c6q5-9c62, UBUNTU-CVE-2017-15227

## What is CVE-2017-15227?

CVE-2017-15227 is a high-severity use after free vulnerability in n/a, published on 22 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Irssi before 1.0.5, while waiting for the channel synchronisation, may incorrectly fail to remove destroyed channels from the query list, resulting in use-after-free conditions when updating the state later on.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2017-15227?

It affects 1 product.


Products: Irssi Irssi.

## How do I fix CVE-2017-15227?

Upgrade to a fixed version.

## Is CVE-2017-15227 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1840](https://insights.sbomify.com/CVE-2002-1840/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2017-10965](https://insights.sbomify.com/CVE-2017-10965/): Null dereference in n/a (critical 9.8)
- [CVE-2017-10966](https://insights.sbomify.com/CVE-2017-10966/): Use after free in n/a (critical 9.8)
- [CVE-2017-7191](https://insights.sbomify.com/CVE-2017-7191/): Use after free in n/a (critical 9.8)
- [CVE-2007-4396](https://insights.sbomify.com/CVE-2007-4396/): Command injection in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15227 and fix it if it is affected.

What it is: CVE-2017-15227 is a high-severity use after free vulnerability in n/a, published on 22 Oct 2017. 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-2017-15227 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-2017-15227/ (Markdown: https://insights.sbomify.com/CVE-2017-15227/index.md)
```

## Sources

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

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