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

> Remote attackers with admin access can execute arbitrary commands via shell metacharacters in the pinghost parameter of the networking configuration page.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-j4rq-g26h-6326

## What is CVE-2013-6829?

CVE-2013-6829 is a high-severity command injection vulnerability in n/a, published on 20 Nov 2013. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

admin/confnetworking.html in PineApp Mail-SeCure allows remote attackers to execute arbitrary commands via shell metacharacters in the pinghost parameter during a ping operation.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Pineapp Mail-Secure.

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

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

## Is CVE-2013-6829 being exploited?

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

Public exploit code:

- PineApp Mail-SeCure test_li_connection.php Arbitrary Command Execution (metasploit)
- PineApp MailSecure - Remote Command Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-4987](https://insights.sbomify.com/CVE-2013-4987/): Command injection in n/a (high 8.5)
- [CVE-2013-6828](https://insights.sbomify.com/CVE-2013-6828/): Auth bypass in n/a (medium 6.4)
- [CVE-2013-6827](https://insights.sbomify.com/CVE-2013-6827/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-6829 is a high-severity command injection vulnerability in n/a, published on 20 Nov 2013. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6829 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-2013-6829/ (Markdown: https://insights.sbomify.com/CVE-2013-6829/index.md)
```

## Sources

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

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