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

> Attackers can gain elevated privileges on Android devices by exploiting an untrusted search path in Superuser applications via a crafted environment variable.

- **Severity:** Critical 10.0 (`AV:N/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:** 30 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qrxj-82j8-48xr

## What is CVE-2013-6774?

CVE-2013-6774 is a critical vulnerability in n/a, published on 30 Mar 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Untrusted search path vulnerability in the ChainsDD Superuser package 3.1.3 for Android 4.2.x and earlier, CyanogenMod/ClockWorkMod/Koush Superuser package 1.0.2.1 for Android 4.2.x and earlier, and Chainfire SuperSU package before 1.69 for Android 4.2.x and earlier allows attackers to load an arbitrary .jar file and gain privileges via a crafted BOOTCLASSPATH environment variable for a /system/xbin/su process.  NOTE: another researcher was unable to reproduce this with ChainsDD Superuser.

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

It affects 3 products.


Products: Androidsu Chainsdd Superuser, Chainfire Supersu, Koushik Dutta Superuser.

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

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

## Is CVE-2013-6774 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-6774 is a critical vulnerability in n/a, published on 30 Mar 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-6774 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-6774/ (Markdown: https://insights.sbomify.com/CVE-2013-6774/index.md)
```

## Sources

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

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