# CVE-2017-15228: Memory corruption in n/a

> An attacker can cause a crash or potentially execute code by providing a theme with unterminated color sequences in Irssi.

- **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-15228, DEBIAN-CVE-2017-15228, GHSA-9pjj-33mj-c4qq, UBUNTU-CVE-2017-15228

## What is CVE-2017-15228?

CVE-2017-15228 is a high-severity memory corruption 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, when installing themes with unterminated colour formatting sequences, may access data beyond the end of the string.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Irssi Irssi.

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

Upgrade to a fixed version.

## Is CVE-2017-15228 being exploited?

There is no known exploitation of CVE-2017-15228 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-15228 and fix it if it is affected.

What it is: CVE-2017-15228 is a high-severity memory corruption 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-15228 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-15228/ (Markdown: https://insights.sbomify.com/CVE-2017-15228/index.md)
```

## Sources

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

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