# CVE-2005-0129: Command injection in n/a

> Remote attackers can execute arbitrary IRC commands in Konversation by exploiting recursive variable expansion in channel names when a user clicks the Part Button.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Jan 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-0129, GHSA-xwmj-j245-94g9

## What is CVE-2005-0129?

CVE-2005-0129 is a high-severity command injection vulnerability in n/a, published on 22 Jan 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Quick Buttons feature in Konversation 0.15 allows remote attackers to execute certain IRC commands via a channel name containing "%" variables, which are recursively expanded by the Server::parseWildcards function when the Part Button is selected.

## Which versions are affected by CVE-2005-0129?

It affects 1 product.


Products: Berlios Konversation.

## How do I fix CVE-2005-0129?

Upgrade to a fixed version.

## Is CVE-2005-0129 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0129 exists.

Public exploit code:

- konversation irc client 0.15 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-0130](https://insights.sbomify.com/CVE-2005-0130/): Command injection in n/a (high 7.5)
- [CVE-2005-0131](https://insights.sbomify.com/CVE-2005-0131/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0129 and fix it if it is affected.

What it is: CVE-2005-0129 is a high-severity command injection vulnerability in n/a, published on 22 Jan 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0129 exists.

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-2005-0129/ (Markdown: https://insights.sbomify.com/CVE-2005-0129/index.md)
```

## Sources

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

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