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

> Remote attackers can execute arbitrary commands via shell metacharacters in the DNS lookup query field of Looking Glass.

- **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:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wjc8-fmf5-j97p

## What is CVE-2005-2777?

CVE-2005-2777 is a high-severity command injection vulnerability in n/a, published on 2 Sep 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Looking Glass 20040427 allows remote attackers to execute arbitrary commands via shell metacharacters in the DNS lookup query field.

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

It affects 1 product.


Products: Looking Glass Looking Glass.

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

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

## Is CVE-2005-2777 being exploited?

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

Public exploit code:

- Looking Glass 20040427 - Remote Command Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-2776](https://insights.sbomify.com/CVE-2005-2776/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2777 is a high-severity command injection vulnerability in n/a, published on 2 Sep 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-2777 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-2777/ (Markdown: https://insights.sbomify.com/CVE-2005-2777/index.md)
```

## Sources

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

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