dbcve.org
SuperuserApplication · Koushik Dutta

CVE-2013-6769

HIGH · 10.0 CVSS v2.0 Published 2014-03-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The CyanogenMod/ClockWorkMod/Koush Superuser package 1.0.2.1 for Android allows attackers to gain privileges via shell metacharacters in the -c option to /system/xbin/su.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Superuser package 1.0.2.1 for Android contains a command injection vulnerability in the /system/xbin/su binary. The -c option, intended to execute a single command as root, fails to properly sanitize shell metacharacters, allowing attackers to inject and execute arbitrary commands with elevated privileges.

MitigationUpdate to a patched version of the CyanogenMod/ClockWorkMod/Koush Superuser package that properly sanitizes input passed to the -c option of the su binary.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SuperuserApplication
Affected:= 1.0.2.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if the Superuser app is installed
    Run 'pm list packages | grep superuser' or check /data/app for Superuser.apk
    Affected if The package com.koushikdutta.superuser is present on the device
  2. Verify the Superuser package version
    Run 'dumpsys package com.koushikdutta.superuser' or check the APK versionName in /data/app
    Affected if The versionName equals 1.0.2.1
  3. Confirm the su binary exists at the vulnerable path
    Check if /system/xbin/su exists using 'ls -la /system/xbin/su'
    Affected if The file /system/xbin/su is present on the system
  4. Identify the su binary version
    Run '/system/xbin/su --version' or use 'strings' on the binary to find version metadata
    Affected if The binary reports version 1.0.2.1 or is the Koushik Dutta Superuser build associated with that release
  5. Review apps or scripts using the -c option
    Check logcat, audit logs, or review any automation scripts that invoke 'su -c <command>'
    Affected if The -c option is used to execute commands on the device, as the vulnerability triggers through unsanitized input passed via this flag

A device is affected if the Koushik Dutta Superuser version 1.0.2.1 is installed with the /system/xbin/su binary present, enabling command injection through the -c option.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of the CyanogenMod/ClockWorkMod/Koush Superuser package that properly sanitizes input passed to the -c option of the su binary.

Fix this in Superuser Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-6769 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-6769 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data