Skip to content
Noroxi
CVE-2018-11277· NVD / CVE Program· CNA qualcomm

In Snapdragon (Automobile, Mobile, Wear) in version MSM8909W, MSM8996AU, SD 210/SD 212/SD 205, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD

In Snapdragon (Automobile, Mobile, Wear) in version MSM8909W, MSM8996AU, SD 210/SD 212/SD 205, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 810, SD 820, SD 820A, SD 835, SD 845, SDA660, the com.qualcomm.embms is a vendor package deployed in the system image which has an inadequate permission level and allows any application installed from Play Store to request this permission at install-time. The system application interfaces with the Radio Interface Layer leading to potential access control issue.

HighCVSS 7.8 · v3.0—No exploit No fix recorded
Published
Sep 20, 2018
Updated
Jun 16, 2026
EPSS
0.2% · 6th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Affected systems

VendorProduct
qualcommmsm8909w firmware
qualcommmsm8909w
qualcommmsm8996au firmware
qualcommmsm8996au
qualcommsd210 firmware
qualcommsd210
qualcommsd212 firmware
qualcommsd212
qualcommsd205 firmware
qualcommsd205
qualcommsd430 firmware
qualcommsd430

and 28 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • qualcomm msm8909w firmwareall versions
  • qualcomm msm8996au firmwareall versions
  • qualcomm sd205 firmwareall versions
  • qualcomm sd210 firmwareall versions
  • qualcomm sd212 firmwareall versions
  • qualcomm sd415 firmwareall versions
  • qualcomm sd430 firmwareall versions
  • qualcomm sd450 firmwareall versions
  • qualcomm sd615 firmwareall versions
  • qualcomm sd616 firmwareall versions
  • qualcomm sd617 firmwareall versions
  • qualcomm sd625 firmwareall versions
  • qualcomm sd650 firmwareall versions
  • qualcomm sd652 firmwareall versions
  • qualcomm sd810 firmwareall versions
  • qualcomm sd820 firmwareall versions
  • qualcomm sd820a firmwareall versions
  • qualcomm sd835 firmwareall versions
  • qualcomm sd845 firmwareall versions
  • qualcomm sda660 firmwareall versions

Versions reported by the vendor

Affected version ranges reported by the assigning authority (qualcomm). Independent of NVD's CPE analysis and usually ahead of it.

  • Qualcomm, Inc. Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear

    • MSM8909W, MSM8996AU, SD 210/SD 212/SD 205, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 810, SD 820, SD 820A, SD 835, SD 845, SDA660affected

Other highest-scoring records for the same primary product.

  • CVE-2017-11076Use of Out-of-range Pointer Offset in Video
    39Monitor
  • CVE-2019-2285Out of bound write issue is observed while giving information about properties that have been set so far for playing video in Snapdragon Aut
    39Monitor
  • CVE-2019-10538Lack of check of address range received from firmware response allows modem to respond arbitrary pages into its address range which can comp
    39Monitor
  • CVE-2019-10509Device record of the pairing device used after free during ACL disconnection in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity
    39Monitor
  • CVE-2019-2259Resource allocation error while playing the video whose dimensions are more than supported dimension in Snapdragon Auto, Snapdragon Compute,
    39Monitor
  • CVE-2019-2255An unprivileged user can craft a bitstream such that the payload encoded in the bitstream gains code execution in Snapdragon Auto, Snapdrago
    39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

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

nvd-primary

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records