dbcve.org
Mdm9615 FirmwareOperating system · Qualcomm

CVE-2014-10057

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-18
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
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
In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile MDM9615, MDM9625, MDM9635M, MDM9640, MDM9650, SD 210/SD 212/SD 205, SD 400, SD 425, SD 430, SD 435, SD 617, SD 625, and Snapdragon_High_Med_2016, binary Calibration files under data/misc/audio have 777 permissions.

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

Vulnerability in Android audio subsystem where binary calibration files under data/misc/audio are created with 777 permissions (rwxrwxrwx), making them world-readable and world-writable. This affects multiple Qualcomm Snapdragon chipsets (MDM9615, MDM9625, MDM9635M, MDM9640, MDM9650, SD 210/212/205, SD 400, SD 425, SD 430, SD 435, SD 617, SD 625, and Snapdragon_High_Med_2016). The overly permissive access allows any application or process on the device to read or modify sensitive audio calibration data, potentially enabling privilege escalation or information disclosure.

MitigationApply the Android security patch from 2018-04-05 or later which corrects file permissions on calibration files. For immediate mitigation, ensure the data/misc/audio directory and its contents have restrictive permissions (600 or 700) rather than 777.

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
Mdm9615 FirmwareOperating system
Affected:all versions
Mdm9625 FirmwareOperating system
Affected:all versions
Mdm9635m FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Sd 210 FirmwareOperating system
Affected:all versions
Sd 212 FirmwareOperating system
Affected:all versions
Sd 205 FirmwareOperating system
Affected:all versions

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 chipset model
    Check the device or firmware information to determine the Qualcomm Snapdragon or MDM chipset in use (e.g., MDM9615, MDM9625, MDM9635M, MDM9640, MDM9650, SD 210, SD 212, SD 205, SD 400, SD 425, SD 430, SD 435, SD 617, SD 625, or Snapdragon_High_Med_2016)
    Affected if The device uses any of the listed affected chipsets
  2. Locate audio calibration directory
    Access the data/misc/audio directory on the device filesystem (via ADB shell or device forensics)
    Affected if The data/misc/audio directory exists on the device
  3. List file permissions in audio directory
    Run 'ls -la /data/misc/audio/' or equivalent command to view permissions of all files in the directory
    Affected if Any file in the directory shows permissions as 777 (rwxrwxrwx) or 666 (rw-rw-rw-) indicating world-readability and world-writability
  4. Verify world-readable/writable bits
    Check the permission bits: if the last three digits are 777 or 666, the file is world-readable (4) and world-writable (2) for all users
    Affected if Files have permission mode containing 7 or 6 in the other/others field (e.g., -rwxrwxrwx, -rw-rw-rw-)

If the device uses an affected Qualcomm chipset AND the data/misc/audio directory exists with files set to 777 or 666 permissions, the environment is vulnerable to this CVE.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Android security patch from 2018-04-05 or later which corrects file permissions on calibration files. For immediate mitigation, ensure the data/misc/audio directory and its contents have restrictive permissions (600 or 700) rather than 777.

Recommended fix High confidence

Android security patch level 2018-04-05 or later for the affected Qualcomm Snapdragon devices

  1. Apply Android security patch level 2018-04-05 or later to the affected device. This patch addresses the overly permissive 777 permissions on binary calibration files under data/misc/audio.
  2. Verify the update was applied successfully by checking the Android security patch level in Settings > About Phone > Security patch level.
  3. If OTA updates are not available, contact the device manufacturer (OEM) for a custom firmware update that includes the April 2018 security patch.
  4. As a verification step after patching, confirm that files in /data/misc/audio no longer have world-writable permissions (should be 640 or stricter).
Caveat Applying security updates may require device reboot and could potentially reset some user configurations; ensure backup of important data before applying updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mdm9615 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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