# openSUSE-SU-2021:0587-1: Security update for irssi

> Multiple memory corruption and null pointer dereference flaws in irssi allow remote attackers to cause denial of service via crafted network packets.

- **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:** 19 Apr 2021

## What is openSUSE-SU-2021:0587-1?

openSUSE-SU-2021:0587-1 is a memory corruption vulnerability in irssi, published on 19 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This update for irssi fixes the following issues:

irssi was updated to 1.2.3 (boo#1184848)

- Fix the compilation of utf8proc (#1021)
- Fix wrong call to free. By Zero King (#1076)
- Fix a colour reset in true colour themes when encountering
  mIRC colours (#1059)
- Fix memory leak on malformed CAP requests (#1120)
- Fix an erroneous free of SASL data. Credit to Oss-Fuzz (#1128,
  #1130)
- Re-set the TLS flag when reconnecting (#1027, #1134)
- Fix the scrollback getting stuck after /clear (#1115, #1136)
- Fix the input of Ctrl+C as the first character (#1153,  #1154)
- Fix crash on quit during unloading of modules on certain
  platforms (#1167)
- Fix Irssi freezing input after Ctrl+Space on GLib >2.62 (#1180,
  #1183)
- Fix layout of IDCHANs. By Lauri Tirkkonen (#1197)
- Fix crash when server got reconnected before it was properly
  connected (#1210, #1211)
- Fix multiple identical active caps (#1249)
- Minor help corrections (#1156, #1213, #1214, #1255)
- Remove erroneous colour in the colorless theme. Reported and
  fixed by Nutchanon Wetchasit (#1220, #1221)
- Fix invalid bounds calculation when editing the text
  entry. Found and fixed by Sergey Valentey (#1269)
- Fix passing of negative size in buffer writes. Found and
  fixed by Sergey Valentey (#1270)
- Fix Irssi freezing on slow hardware and fast DCC transfers (#159,
  #1271)
- Fix compilation on Solaris (#1291)
- Fix null pointer dereference when receiving broken JOIN
  record. Credit to Oss-Fuzz (#1292)
- Fix crash on /connect to some sockets (#1239, #1298)
- Fix Irssi rendering on Apple ARM. By Misty De M�o (#1267,
  #1268, #1290)
- Fix crash on /lastlog with broken lines (#1281, #1299)
- Fix memory leak when receiving bogus SASL authentication
  data. Found and fixed by Sergey Valentey (#1293)

## Which versions are affected by openSUSE-SU-2021:0587-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `irssi` | openSUSE:Leap 15.2 | All versions | 1.2.3-lp152.3.3.1 |

## How do I fix openSUSE-SU-2021:0587-1?

Upgrade to a fixed version.

## Is openSUSE-SU-2021:0587-1 being exploited?

There is no known exploitation of openSUSE-SU-2021:0587-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for openSUSE-SU-2021:0587-1 and fix it if it is affected.

What it is: openSUSE-SU-2021:0587-1 is a memory corruption vulnerability in irssi, published on 19 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of openSUSE-SU-2021:0587-1 in the wild and no public exploit code.

Affected product: irssi. 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/openSUSE-SU-2021-0587-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2021-0587-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2021:0587-1

---
From sbomify Insights: https://insights.sbomify.com/openSUSE-SU-2021-0587-1/
Summaries are generated and may contain mistakes; the official description above is the record.