# CVE-2007-2951: Command injection in n/a

> Remote attackers can execute arbitrary commands via shell metacharacters in IRC URIs, requiring user interaction to click the link.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 26 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-2951, GHSA-vvgp-7gw4-m5xw

## What is CVE-2007-2951?

CVE-2007-2951 is a critical command injection vulnerability in n/a, published on 26 Jun 2007. 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 parseIrcUrl function in src/kvirc/kernel/kvi_ircurl.cpp in KVIrc 3.2.0 allows user-assisted remote attackers to execute arbitrary commands via shell metacharacters in an (1) irc:// or (2) irc6:// URI.

## Which versions are affected by CVE-2007-2951?

It affects 1 product.


Products: Kvirc Irc Client.

## How do I fix CVE-2007-2951?

Upgrade to a fixed version.

## Is CVE-2007-2951 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-1999-1351](https://insights.sbomify.com/CVE-1999-1351/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2951 and fix it if it is affected.

What it is: CVE-2007-2951 is a critical command injection vulnerability in n/a, published on 26 Jun 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-2951 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-2007-2951/ (Markdown: https://insights.sbomify.com/CVE-2007-2951/index.md)
```

## Sources

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

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