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

> Remote attackers can execute arbitrary commands via shell metacharacters in the file_name parameter of the SCM component.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-grqj-6rf9-478m

## What is CVE-2005-1752?

CVE-2005-1752 is a medium-severity command injection vulnerability in n/a, published on 21 May 2006. It can be exploited over the network, with no action from the victim.

### Official description

viewFile.php in the scm component of Gforge before 4.0 allows remote attackers to execute arbitrary commands via shell metacharacters in the file_name parameter.

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

It affects 1 product.


Products: Gforge Gforge.

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

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

## Is CVE-2005-1752 being exploited?

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

Public exploit code:

- GForge 3.x - Arbitrary Command Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-4070](https://insights.sbomify.com/CVE-2009-4070/): SQL injection in n/a (high 7.5)
- [CVE-2008-6187](https://insights.sbomify.com/CVE-2008-6187/): SQL injection in n/a (high 7.5)
- [CVE-2008-6188](https://insights.sbomify.com/CVE-2008-6188/): SQL injection in n/a (high 7.5)
- [CVE-2008-6189](https://insights.sbomify.com/CVE-2008-6189/): SQL injection in n/a (high 7.5)
- [CVE-2008-2381](https://insights.sbomify.com/CVE-2008-2381/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-1752 is a medium-severity command injection vulnerability in n/a, published on 21 May 2006. It can be exploited 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-1752 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-1752/ (Markdown: https://insights.sbomify.com/CVE-2005-1752/index.md)
```

## Sources

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

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