CVE-2018-11267: Qualcomm, Inc. Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear: Improper Validation of Array Index

Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified

What, why and how

In Snapdragon (Automobile, Mobile, Wear) in version MDM9206, MDM9607, MDM9615, MDM9640, MDM9650, MDM9655, MSM8996AU, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 600, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 820, SD 820A, SD 835, SD 845, SD 850, SDA660, SDM429, SDM439, SDM630, SDM632, SDM636, SDM660, SDX20, Snapdragon_High_Med_2016, when sending an malformed XML data to deviceprogrammer/firehose it may do an out of bounds buffer write allowing a region of memory to be filled with 0x20.

What

Why

The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Why

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: local access → Improper Validation of Array Index → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Local
Privileges required: Low: a basic authenticated account is required
User interaction: None
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-129 ↗
CWE-129: Improper Validation of Array Index. The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Common Vulnerability Scoring System 3.0: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land: The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.

CWE-129

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2018-3307Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

CERT-FR · French · CERTFR-2018-AVI-582Multiples vulnérabilités dans Google Android

ERecord?id=CVE-2017-18328 Référence CVE CVE-2017-18329 https://www.cve.org/CVERecord?id=CVE-2017-18329 Référence CVE CVE-2017-18330 https://www.cve.org/CVERecord?id=CVE-2017-18330 Référence CVE CVE-2017-18331 https://www.cve.org/CVERecord?id=CVE-2017-18331 Référence CVE CVE-2017-18332 https://www.cve.org/CVERecord?id=CVE-2017-18332 Référence CVE CVE-2017-5754 https://www.cve.org/CVERecord?id=CVE-2017-5754 Référence CVE CVE-2017-8248 https://www.cve.org/CVERecord?id=CVE-2017-8248 Référence CVE CVE-2017-8276 https://www.cve.org/CVERecord?id=CVE-2017-8276 Référence CVE CVE-2018-10840 https://www.cve.org/CVERecord?id=CVE-2018-10840 Référence CVE CVE-2018-11267 https://www.cve.org/CVERecord?id=CVE-2018-11267 Référence CVE CVE-2018-11279 https://www.cve.org/CVERecord?id=CVE-2018-11279 Référence CVE CVE-2018-11922 https://www.cve.org/CVERecord?id=CVE-2018-11922 Référence CVE CVE-2018-11960 https://www.cve.org/CVERecord?id=CVE-2018-11960 Référence CVE CVE-2018-11961 https://www.cve.org/CVERecord?id=CVE-2018-11961 Référence CVE CVE-2018-11963 https://www.cve.org/CVERecord?id=CVE-2018-11963 Référence CVE CVE-2018-11987 https://www.cve.org/CVERecord?id=CVE-2018-11987 Référence CVE CVE-2018-11999 https://www.cve.org/CVERecord?id=CVE-2018-11999 Référence CVE CVE-2018-3595 https://www.cve.org/CVERecord?id=C

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2018-010813複数の Snapdragon 製品における配列インデックスの検証に関する脆弱性

Snapdragon (Automobile、Mobile、Wear) には、配列インデックスの検証に関する脆弱性が存在します。

Official advisory ↗

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Fix not verified
Affected: Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear: MDM9206, MDM9607, MDM9615, MDM9640, MDM9650, MDM9655, MSM8996AU, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 600, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 820, SD 820A, SD 835, SD 845, SD 850, SDA660, SDM429, SDM439, SDM630, SDM632, SDM636, SDM660, SDX20, Snapdragon_High_Med_2016
Fixed: No fixed version is explicitly recorded in the structured CVE data.
Action: No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround: No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.

Evidence and provenance

Published 20 Sept 2018 · Last source change 5 Aug 2024, 08:01 UTC · CWE-129 · Improper Validation of Array Index

CVE recordCVE.org · 5.1

CVSS sourceNIST NVD

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-09-01

European sourceENISA EUVD · EUVD-2018-3307

Product sourceCNA

Remediation sourceCVE/CNA references

CWE sourceNIST NVD

NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

5 Aug 2024, 08:01 UTC
Vendor guidanceAuthoritative vendor guidance changed from no authoritative guidance recorded to vendor advisory.
Before
no authoritative guidance recorded
After
vendor advisory
af854a3a-2127-422b-91ae-364da2661108 ↗
5 Aug 2024, 08:01 UTC
SeveritySeverity changed from Unknown to High.
Before
Unknown
After
High
NIST NVD ↗
5 Aug 2024, 08:01 UTC
CVSS scoreCVSS score changed from not recorded to 7.8 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
Before
not recorded
After
7.8 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)
NIST NVD ↗
1 Sept 2026, 02:42 UTC
ENISA EUVD mappingEUVD-2018-3307 was added to the official ENISA EUVD mapping for this CVE.
Before
not recorded
After
{"euvdId":"EUVD-2018-3307"}
ENISA EUVD ↗
5 Aug 2024, 08:01 UTC
Catalogue recordCVE added to the BlackTree catalogue.
CNA ↗

2018-09-20CVE published

ENISA EUVD · EUVD-2018-3307↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

Qualcomm, Inc. Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear: Improper Validation of Array Index

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

ENISA European Vulnerability Database

EUVD-2018-3307

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication

Qualcomm, Inc. Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear: Improper Validation of Array Index

National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

EUVD-2018-3307

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.