# CVE-2013-4663: Command injection in n/a

> Remote attackers can execute arbitrary commands via shell metacharacters in the Redmine Git Hosting plugin.

- **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:** 28 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mhj8-pmrq-xphp

## What is CVE-2013-4663?

CVE-2013-4663 is a high-severity command injection vulnerability in n/a, published on 28 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

git_http_controller.rb in the redmine_git_hosting plugin for Redmine allows remote attackers to execute arbitrary commands via shell metacharacters in (1) the service parameter to info/refs, related to the get_info_refs function or (2) the reqfile argument to the file_exists function.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2013-4663?

It affects 1 product.


Products: Redmine Redmine Git Hosting Plugin.

## How do I fix CVE-2013-4663?

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

## Is CVE-2013-4663 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4663 and fix it if it is affected.

What it is: CVE-2013-4663 is a high-severity command injection vulnerability in n/a, published on 28 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-4663 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-2013-4663/ (Markdown: https://insights.sbomify.com/CVE-2013-4663/index.md)
```

## Sources

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

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