NVD / CVE Program· CNA qualcomm

CVE-2017-18144: In Android before security patch level 2018-04-05 on Qualcomm Snapdragon Mobile and Snapdragon Wear MSM8909W, SD 210/SD 212/SD 205, SD 450,

Noroxi assessment

Priority: Monitor (action score 39/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 67.7% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In Android before security patch level 2018-04-05 on Qualcomm Snapdragon Mobile and Snapdragon Wear MSM8909W, SD 210/SD 212/SD 205, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 820, SD 835, SD 845, while processing the retransmission of WPA supplicant command send failures, there is a make after break of the connection to WPA supplicant where the local pointer is not properly updated. If the WPA supplicant command transmission fails, a Use After Free condition will occur.

CriticalCVSS 9.8 · v3.0—No exploit No fix recorded

BDU:2018-00856

Published: Apr 11, 2018
Updated: Jun 16, 2026
EPSS: 1.1% · 67th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.1%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
qualcomm	msm8909w firmware	cpe:2.3:o:qualcomm:msm8909w_firmware
qualcomm	msm8909w	cpe:2.3:h:qualcomm:msm8909w
qualcomm	sd 210 firmware	cpe:2.3:o:qualcomm:sd_210_firmware
qualcomm	sd 210	cpe:2.3:h:qualcomm:sd_210
qualcomm	sd 212 firmware	cpe:2.3:o:qualcomm:sd_212_firmware
qualcomm	sd 212	cpe:2.3:h:qualcomm:sd_212
qualcomm	sd 205 firmware	cpe:2.3:o:qualcomm:sd_205_firmware
qualcomm	sd 205	cpe:2.3:h:qualcomm:sd_205
qualcomm	sd 450 firmware	cpe:2.3:o:qualcomm:sd_450_firmware
qualcomm	sd 450	cpe:2.3:h:qualcomm:sd_450
qualcomm	sd 615 firmware	cpe:2.3:o:qualcomm:sd_615_firmware
qualcomm	sd 615	cpe:2.3:h:qualcomm:sd_615

and 16 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 sd 205 firmwareall versions
qualcomm sd 210 firmwareall versions
qualcomm sd 212 firmwareall versions
qualcomm sd 415 firmwareall versions
qualcomm sd 450 firmwareall versions
qualcomm sd 615 firmwareall versions
qualcomm sd 616 firmwareall versions
qualcomm sd 625 firmwareall versions
qualcomm sd 650 firmwareall versions
qualcomm sd 652 firmwareall versions
qualcomm sd 820 firmwareall versions
qualcomm sd 835 firmwareall versions
qualcomm sd 845 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 Mobile, Snapdragon Wear
- MSM8909W, SD 210/SD 212/SD 205, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 820, SD 835, SD 845affected

Same product

qualcomm: all records

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

Published before and after this one in the same product

← EarlierCVE-2017-18127Apr 11, 2018 · In Android before security patch level 2018-04-05 on Qualcomm Snapdragon Mobile and Snapdragon Wear MSM8909W, SD 210/SD 212/SD 205, SD 430,
39Monitor
Later →CVE-2017-18145Apr 11, 2018 · In Android before security patch level 2018-04-05 on Qualcomm Snapdragon Mobile and Snapdragon Wear MSM8909W, SD 210/SD 212/SD 205, SD 450,
39Monitor
Later →CVE-2018-3590Apr 11, 2018 · In Android before security patch level 2018-04-05 on Qualcomm Snapdragon Mobile and Snapdragon Wear MSM8909W, SD 210/SD 212/SD 205, SD 450,
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.

No history yet (it accumulates with the daily EPSS job).

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.

Credits

All researchers

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

Anyone who can reach it over the internet can trigger it.
No account or password is required.
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: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

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

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

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

References

www.securityfocus.com/bid/103671

Show all references (1 more)

source.android.com/security/bulletin/2018-04-01

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

All records