Skip to content
Noroxi
CVE-2017-18312· NVD / CVE Program· CNA qualcomm

While accessing SafeSwitch services, third party can manipulate a given device and perform unauthorized operation due to lack of checking of

While accessing SafeSwitch services, third party can manipulate a given device and perform unauthorized operation due to lack of checking of same state transitions in Snapdragon Automobile, Snapdragon Mobile in version MSM8996AU, SD 410/12, SD 617, SD 650/52, SD 810, SD 820, SD 820A

HighCVSS 7.8 · v3.0—No exploit No fix recorded
Published
Oct 23, 2018
Updated
Jun 16, 2026
EPSS
0.2% · 7th 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
qualcommmsm8996au firmware
qualcommmsm8996au
qualcommsd 410 firmware
qualcommsd 410
qualcommsd 412 firmware
qualcommsd 412
qualcommsd 617 firmware
qualcommsd 617
qualcommsd 650 firmware
qualcommsd 650
qualcommsd 652 firmware
qualcommsd 652

and 6 more

Affected versions

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

  • qualcomm msm8996au firmwareall versions
  • qualcomm sd 410 firmwareall versions
  • qualcomm sd 412 firmwareall versions
  • qualcomm sd 617 firmwareall versions
  • qualcomm sd 650 firmwareall versions
  • qualcomm sd 652 firmwareall versions
  • qualcomm sd 810 firmwareall versions
  • qualcomm sd 820 firmwareall versions
  • qualcomm sd 820a 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

    • MSM8996AU, SD 410/12, SD 617, SD 650/52, SD 810, SD 820, SD 820Aaffected

Other highest-scoring records for the same primary product.

  • CVE-2017-18318Missing validation check on CRL issuer name in Snapdragon Automobile, Snapdragon Mobile in versions MSM8996AU, SD 410/12, SD 425, SD 430, SD
    39Monitor
  • CVE-2024-53030Improper Input Validation in Automotive OS Platform
    31Monitor
  • CVE-2024-45555Integer Overflow to Buffer Overflow in Automotive OS Platform
    31Monitor
  • CVE-2022-33282Integer overflow to buffer overflow in Automotive Multimedia
    31Monitor
  • CVE-2022-25680Memory corruption in multimedia due to buffer overflow while processing count variable from client in Snapdragon Auto
    31Monitor
  • CVE-2019-2277Out of bound read can happen due to lack of NULL termination on user controlled data in WLAN in Snapdragon Auto, Snapdragon Compute, Snapdra
    31Monitor

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

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

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

All records