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

> Authenticated users can execute arbitrary commands via shell metacharacters in the SquirrelMail GPG plugin parameters.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-87rp-52qv-ghjc

## What is CVE-2005-1924?

CVE-2005-1924 is a critical command injection vulnerability in n/a, published on 15 Jul 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The G/PGP (GPG) Plugin 2.1 and earlier for Squirrelmail allow remote authenticated users to execute arbitrary commands via shell metacharacters in (1) the fpr parameter to the deleteKey function in gpg_keyring.php, as called by (a) import_key_file.php, (b) import_key_text.php, and (c) keyring_main.php; and (2) the keyserver parameter to the gpg_recv_key function in gpg_key_functions.php, as called by gpg_options.php.  NOTE: this issue may overlap CVE-2007-3636.

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

It affects 1 product.


Products: Squirrelmail Gpg Plugin.

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

No fix has been published for CVE-2005-1924 yet. Limit exposure of the affected software until one is available.

## Is CVE-2005-1924 being exploited?

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

Public exploit code:

- SquirrelMail G/PGP Encryption Plugin 2.0 - Command Execution (exploitdb)
- SquirrelMail G/PGP Encryption Plugin - 'deletekey()' Command Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-3778](https://insights.sbomify.com/CVE-2007-3778/): Command injection in n/a (high 7.5)
- [CVE-2007-3636](https://insights.sbomify.com/CVE-2007-3636/): Command injection in n/a (high 7.5)
- [CVE-2007-3634](https://insights.sbomify.com/CVE-2007-3634/): Command injection in n/a (medium 6.5)
- [CVE-2006-4169](https://insights.sbomify.com/CVE-2006-4169/): Path traversal in n/a (medium 5.5)
- [CVE-2007-3779](https://insights.sbomify.com/CVE-2007-3779/): Path traversal in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-1924 is a critical command injection vulnerability in n/a, published on 15 Jul 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1924 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-1924/ (Markdown: https://insights.sbomify.com/CVE-2005-1924/index.md)
```

## Sources

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

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