# openSUSE-SU-2017:0739-1: Security update for irssi

> A use-after-free vulnerability in the IRC client irssi allows remote attackers to execute arbitrary code or cause a denial of service.

- **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:** 17 Mar 2017

## What is openSUSE-SU-2017:0739-1?

openSUSE-SU-2017:0739-1 is an use after free vulnerability in irssi, published on 17 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This update to irssi 1.0.2 fixes security issues and bugs.

The following vulnerabilities were fixed:

boo#1029020: Use after free while producing list of netjoins

The following non-security changes are included:

- Fix in command arg parser to detect missing arguments in tail place
- Fix regression that broke incoming DCC file transfers
- Fix issue with escaping \ in evaluated strings
- improve UTF8 support in GRegex

## Which versions are affected by openSUSE-SU-2017:0739-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `irssi` | SUSE:Package Hub 12 | All versions | 1.0.2-21.1 |

## How do I fix openSUSE-SU-2017:0739-1?

Upgrade to a fixed version.

## Is openSUSE-SU-2017:0739-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: openSUSE-SU-2017:0739-1 is an use after free vulnerability in irssi, published on 17 Mar 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 openSUSE-SU-2017:0739-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-2017-0739-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2017-0739-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2017:0739-1

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