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

> Attackers can execute shell commands via a contributed script in the Gadu Gadu client, potentially compromising the user's system.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 19 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p7c6-qq8c-xjcm

## What is CVE-2005-1851?

CVE-2005-1851 is a critical command injection vulnerability in n/a, published on 19 Jul 2005. 

### Official description

A certain contributed script for ekg Gadu Gadu client 1.5 and earlier allows attackers to execute shell commands via unknown attack vectors.

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

It affects 1 product.


Products: Ekg Ekg.

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

Upgrade to a fixed version.

## Is CVE-2005-1851 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-1850](https://insights.sbomify.com/CVE-2005-1850/): Other in n/a (critical 10.0)
- [CVE-2005-2369](https://insights.sbomify.com/CVE-2005-2369/): Integer overflow in n/a (high 7.5)
- [CVE-2007-1663](https://insights.sbomify.com/CVE-2007-1663/): Denial of service in n/a (medium 5.0)
- [CVE-2007-1664](https://insights.sbomify.com/CVE-2007-1664/): Null dereference in n/a (medium 5.0)
- [CVE-2007-1665](https://insights.sbomify.com/CVE-2007-1665/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-1851 is a critical command injection vulnerability in n/a, published on 19 Jul 2005. 
Exploitation: There is no known exploitation of CVE-2005-1851 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-2005-1851/ (Markdown: https://insights.sbomify.com/CVE-2005-1851/index.md)
```

## Sources

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

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