dbcve.org
Android MsmOperating system · Codeaurora

CVE-2013-2599

MEDIUM · 5.0 CVSS v2.0 Published 2014-08-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
A certain Qualcomm Innovation Center (QuIC) patch to the NativeDaemonConnector class in services/java/com/android/server/NativeDaemonConnector.java in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.3.x enables debug logging, which allows attackers to obtain sensitive disk-encryption passwords via a logcat call.

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

A debug logging feature in the NativeDaemonConnector class (services/java/com/android/server/NativeDaemonConnector.java) in Code Aurora Forum Android 4.1.x-4.3.x releases was left enabled, causing sensitive disk-encryption passwords to be written to logcat. Attackers with READ_LOGS permission can extract these passwords.

MitigationDisable debug logging in the NativeDaemonConnector class to prevent sensitive data from being written to system logs; consider restricting or revoking READ_LOGS permission from untrusted applications.

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
Android MsmOperating system
Affected:= 3.2.54= 3.2.55= 3.2.56= 3.2.57= 3.2.58= 3.2.59= 3.2.60= 3.2.61= 3.2.62= 3.4.72= 3.4.73= 3.4.74

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
Partial
Integrity
None
Availability
None

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

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. Identify the Code Aurora Forum Android version
    Check the system property 'ro.build.version.au' or the baseband/kernel version information that contains the Code Aurora release identifier (e.g., via 'getprop' or in Build info)
    Affected if The version matches 3.2.54 through 3.2.62 or 3.4.72 through 3.4.74
  2. Confirm the Android version is 4.1.x-4.3.x
    Check 'ro.build.version.release' system property or the Settings > About Phone > Android version display
    Affected if The device runs Android 4.1.x, 4.2.x, or 4.3.x in combination with the vulnerable Code Aurora versions above
  3. Inspect NativeDaemonConnector.java for debug logging
    Locate the file services/java/com/android/server/NativeDaemonConnector.java in the device system image or source tree and search for debug print statements that output sensitive parameters (e.g., password strings being logged)
    Affected if Debug logging code is present and writes disk-encryption related data to system logs
  4. Check for encryption password leakage in logcat
    Run 'logcat -d' or 'logcat -v threadtime' and search for patterns containing 'encrypt' or 'password' in daemon log entries originating from NativeDaemonConnector
    Affected if Logcat output contains disk-encryption passwords or sensitive credential data
  5. Enumerate apps with READ_LOGS permission
    Use 'dumpsys package' or check app permissions via Settings > Apps > Permissions to list applications granted the READ_LOGS permission
    Affected if Any untrusted third-party application holds the READ_LOGS permission

A device is affected if it runs Code Aurora Forum Android versions 3.2.54-3.2.62 or 3.4.72-3.4.74 (Android 4.1.x-4.3.x) with debug logging enabled in NativeDaemonConnector, exposing encryption passwords to any app holding READ_LOGS permission.

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

Disable debug logging in the NativeDaemonConnector class to prevent sensitive data from being written to system logs; consider restricting or revoking READ_LOGS permission from untrusted applications.

Fix this in Android Msm Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-2599 — 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-2599 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