CVE-2019-10531: Qualcomm, Inc. Snapdragon Auto, Snapdragon Mobile, Snapdragon Wearables: Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Recommended actionWithin 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Patch available

What, why and how

Incorrect reading of system image resulting in buffer overflow when size of system image is increased in Snapdragon Auto, Snapdragon Mobile, Snapdragon Wearables in MDM9607, MSM8909W, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 439 / SD 429, SD 450, SD 625, SD 632, SDM439

What

Why

The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Why

The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.

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: a network path → Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Network
Privileges required: None: unauthenticated exploitation is possible
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-120 ↗
CWE-120: Buffer Copy without Checking Size of Input ('Classic Buffer Overflow'). The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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: No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.

NetworkUnauthenticatedCWE-120

Official authority intelligence

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

ENISA EUVD · EUVD-2019-2335Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

CERT-FR · French · CERTFR-2019-AVI-425Multiples vulnérabilités dans Google Android

d?id=CVE-2019-10495 Référence CVE CVE-2019-10496 https://www.cve.org/CVERecord?id=CVE-2019-10496 Référence CVE CVE-2019-10504 https://www.cve.org/CVERecord?id=CVE-2019-10504 Référence CVE CVE-2019-10505 https://www.cve.org/CVERecord?id=CVE-2019-10505 Référence CVE CVE-2019-10512 https://www.cve.org/CVERecord?id=CVE-2019-10512 Référence CVE CVE-2019-10515 https://www.cve.org/CVERecord?id=CVE-2019-10515 Référence CVE CVE-2019-10522 https://www.cve.org/CVERecord?id=CVE-2019-10522 Référence CVE CVE-2019-10524 https://www.cve.org/CVERecord?id=CVE-2019-10524 Référence CVE CVE-2019-10529 https://www.cve.org/CVERecord?id=CVE-2019-10529 Référence CVE CVE-2019-10531 https://www.cve.org/CVERecord?id=CVE-2019-10531 Référence CVE CVE-2019-10533 https://www.cve.org/CVERecord?id=CVE-2019-10533 Référence CVE CVE-2019-10534 https://www.cve.org/CVERecord?id=CVE-2019-10534 Référence CVE CVE-2019-10541 https://www.cve.org/CVERecord?id=CVE-2019-10541 Référence CVE CVE-2019-2103 https://www.cve.org/CVERecord?id=CVE-2019-2103 Référence CVE CVE-2019-2108 https://www.cve.org/CVERecord?id=CVE-2019-2108 Référence CVE CVE-2019-2115 https://www.cve.org/CVERecord?id=CVE-2019-2115 Référence CVE CVE-2019-2123 https://www.cve.org/CVERecord?id=CVE-2019-2123 Référence CVE CVE-2019-2124 https://www.cve.org/CVERecord?id=CVE-2019-

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2019-011681複数の Snapdragon 製品における古典的バッファオーバーフローの脆弱性

複数の Snapdragon 製品には、古典的バッファオーバーフローの脆弱性が存在します。

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.: Patch available
Affected: Snapdragon Auto, Snapdragon Mobile, Snapdragon Wearables: MDM9607, MSM8909W, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 439 / SD 429, SD 450, SD 625, SD 632, SDM439
Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action: Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround: No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.

Evidence and provenance

Published 6 Nov 2019 · Last source change 4 Aug 2024, 22:24 UTC · CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

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-2019-2335

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 ↗

1 Sep 2026, 02:42 UTC
ENISA EUVD mappingEUVD-2019-2335 was added to the official ENISA EUVD mapping for this CVE.
Before
not recorded
After
{"euvdId":"EUVD-2019-2335"}
ENISA EUVD ↗
4 Aug 2024, 22:24 UTC
Vendor guidanceAuthoritative vendor guidance changed: added patch: source.android.com/bulletin; added remediation: source.android.com/bulletin.
Before
no authoritative guidance recorded
After
patch: source.android.com/bulletin · remediation: source.android.com/bulletin
source.android.com ↗
4 Aug 2024, 22:24 UTC
Affected versionsThe structured affected or fixed version information changed.
Before
MDM9607, MSM8909W, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 439 / SD 429, SD 450, SD 625, SD 632, SDM439 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
After
MDM9607, MSM8909W, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 439 / SD 429, SD 450, SD 625, SD 632, SDM439 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
CNA ↗
4 Aug 2024, 22:24 UTC
Remediation statusRemediation status changed from Awaiting fix to Patch available.
Before
Awaiting fix
After
Patch available
source.android.com ↗
4 Aug 2024, 22:24 UTC
SeveritySeverity changed from Unknown to Critical.
Before
Unknown
After
Critical
NIST NVD ↗
4 Aug 2024, 22:24 UTC
CVSS scoreCVSS score changed from not recorded to 9.8 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
Before
not recorded
After
9.8 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
NIST NVD ↗
4 Aug 2024, 22:24 UTC
Catalogue recordCVE added to the BlackTree catalogue.
CNA ↗

2019-11-06CVE published

2024-08-04Fixed release or patch reference recorded

ENISA EUVD · EUVD-2019-2335↗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 Auto, Snapdragon Mobile, Snapdragon Wearables: Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Published severity in operational context

Evidence used

Compensating controls

Verification

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-2019-2335