# CVE-2012-6567: Command injection in n/a

> Authenticated users can execute arbitrary commands via shell metacharacters in custom rule logic, requiring an upgrade to secure the application.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **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:** 17 Jun 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qv7j-w8h6-h293

## What is CVE-2012-6567?

CVE-2012-6567 is a medium-severity command injection vulnerability in n/a, published on 17 Jun 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

REDCap before 4.14.0 allows remote authenticated users to execute arbitrary commands via shell metacharacters in the logic of a custom rule.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2012-6567?

It affects 1 product.


Products: Project-Redcap Redcap.

## How do I fix CVE-2012-6567?

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

## Is CVE-2012-6567 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-4610](https://insights.sbomify.com/CVE-2013-4610/): Other in n/a (critical 10.0)
- [CVE-2013-4611](https://insights.sbomify.com/CVE-2013-4611/): Other in n/a (critical 10.0)
- [CVE-2013-4609](https://insights.sbomify.com/CVE-2013-4609/): Security feature bypass in n/a (medium 6.5)
- [CVE-2013-4608](https://insights.sbomify.com/CVE-2013-4608/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2013-4612](https://insights.sbomify.com/CVE-2013-4612/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-6567 and fix it if it is affected.

What it is: CVE-2012-6567 is a medium-severity command injection vulnerability in n/a, published on 17 Jun 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-6567 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-2012-6567/ (Markdown: https://insights.sbomify.com/CVE-2012-6567/index.md)
```

## Sources

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

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