dbcve.org
Mdm9607 FirmwareOperating system · Qualcomm

CVE-2018-11855

HIGH · 7.8 CVSS v3.0 Published 2019-02-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
If an end user makes use of SCP11 sample OCE code without modification it could lead to a buffer overflow when transmitting a CAPDU in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT and Snapdragon Mobile in versions MDM9607, MDM9650, MDM9655, MSM8996AU, SD 210/SD 212/SD 205, SD 410/12, SD 636, SD 820, SD 820A, SD 835, SD 8CX, SDA660, SDM630, SDM660.

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 · moderate confidence

A buffer overflow vulnerability exists in the SCP11 sample OCE (Open Card Environment) code when transmitting CAPDUs (Command Application Data Units). The vulnerability stems from insufficient bounds checking during CAPDU transmission, allowing memory corruption that could enable code execution or denial of service.

MitigationIf using the affected SCP11 sample OCE code, implement proper buffer size validation and bounds checking before transmitting CAPDUs; otherwise, obtain and deploy firmware updates from the device manufacturer once available.

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
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Mdm9655 FirmwareOperating system
Affected:all versions
Msm8996au 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
Sd 410 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/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 the Qualcomm chipset in the device
    Check the device hardware specifications, boot logs, or system information to determine the exact Qualcomm processor model (e.g., Mdm9607, Mdm9650, Mdm9655, Msm8996au, Sd 210, Sd 212, Sd 205, or Sd 410)
    Affected if The device contains any of the following chips: Mdm9607, Mdm9650, Mdm9655, Msm8996au, Sd 210, Sd 212, Sd 205, or Sd 410
  2. Check the firmware version
    Access the device firmware information through manufacturer documentation, boot logs, or firmware extraction tools. Compare the firmware version against the affected product list
    Affected if The device firmware corresponds to any of the listed Qualcomm chips (all versions are affected)
  3. Determine if SCP11 OCE code is present
    Inspect the firmware image or source code for the presence of SCP11 (Secure Channel Protocol 11) and OCE (Open Card Environment) implementation files or modules
    Affected if The firmware contains SCP11 sample OCE code used for smart card communication
  4. Identify CAPDU transmission functionality
    Search the codebase for CAPDU (Command Application Data Unit) handling functions, particularly those involved in transmitting data between the device and smart card
    Affected if The device implements CAPDU transmission routines as part of smart card communication
  5. Inspect bounds checking in CAPDU handling
    Review the CAPDU transmission code for buffer size validation and boundary checks before memory operations. Look for unsafe functions like memcpy, strcpy, or manual pointer arithmetic without prior size validation
    Affected if The CAPDU transmission code lacks proper buffer size validation or contains unchecked buffer operations

A device is affected if it uses any of the listed Qualcomm chipsets (Mdm9607, Mdm9650, Mdm9655, Msm8996au, Sd 210, Sd 212, Sd 205, or Sd 410) and runs firmware containing the SCP11 sample OCE code with CAPDU transmission that lacks proper bounds checking.

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

If using the affected SCP11 sample OCE code, implement proper buffer size validation and bounds checking before transmitting CAPDUs; otherwise, obtain and deploy firmware updates from the device manufacturer once available.

Fix this in Mdm9607 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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