# CVE-2013-6831: Privilege escalation in n/a

> Local attackers can escalate privileges to root by exploiting overly permissive sudo rules for the qmailq account in PineApp Mail-SeCure.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-xm2w-p5xp-2rc6

## What is CVE-2013-6831?

CVE-2013-6831 is a high-severity vulnerability in n/a, published on 20 Nov 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

PineApp Mail-SeCure 3.70 and earlier on 5099SK and earlier platforms has a sudoers file that does not properly restrict user specifications, which allows local users to gain privileges via a sudo command that leverages access to the qmailq account.

Weakness: CWE-264

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

It affects 1 product.


Products: Pineapp Mail-Secure 5099sk.

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

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

## Is CVE-2013-6831 being exploited?

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

Public exploit code:

- PineApp MailSecure - Remote Command Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-6830](https://insights.sbomify.com/CVE-2013-6830/): Command injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-6831 is a high-severity vulnerability in n/a, published on 20 Nov 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6831 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-6831/ (Markdown: https://insights.sbomify.com/CVE-2013-6831/index.md)
```

## Sources

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

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