Home/CVE/Out of bound write issue is observed while giving information about properties that have been set so far for playing vid
CVE
CVE-2019-22851
Out of bound write issue is observed while giving information about properties that have been set so far for playing vid
Out of bound write issue is observed while giving information about properties that have been set so far for playing video in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in MSM8909W, MSM8996AU, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 625, SD 632, SD 636, SD 665, SD 675, SD 712 / SD 710 / SD 670, SD 730, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 855, SD 8CX, SDA660, SDM439, SDM630, SDM660, Snapdragon_High_Med_2016, SXR1130.
CRITICAL · CVSS 9.8
EPSS 0.01093
EPSS exploitation odds1.09% · top 37%
Act now
- Public exploit or PoC is available
- CVSS base score ≥ 7.0
No Sigma yet — build one →
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2019-2285, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
⚠
Exploitation evidence
1 of 7 sources
Corroboration score 8/100 ·
emerging.
This counts how many independent sources have exploitation evidence, and separates two different things:
confirmed in-the-wild use (CISA KEV, Microsoft MSRC, ransomware activity) from
exploit / PoC availability (Metasploit, ExploitDB, Nuclei, public PoCs). A template or PoC existing means
an attack is possible and easy - it is not, on its own, proof the CVE is being exploited in the wild.
Exploit / PoC available
public PoC
↗
Exploitation momentum
484 days of EPSSdormant
Flat and low - no real exploitation pressure. This reads the direction and speed of EPSS over time, which can move before EPSS itself peaks or before CISA lists it.
EPSS exploitation probability
1.09%
Top 37%odds of exploitation in the next 30 days
CVSS metric silhouette
shape grows toward worst-case
SSVC triage
No SSVC vulnrichment for this CVE. CISA's Vulnrichment program scores newer CVEs (~2024 onwards) plus selected older critical ones. Use the EPSS probability + KEV status to triage instead.
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Impact - what breaks
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
VECTOR
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HLifecycle
- 06 Nov 2019Published to NVD
- 17 Jun 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
Attack path
Full kill chain
⚠
Public Exploits & PoCs
1These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted. Signed-in users mark whether it works, rate 1-10, and can report malware with a required reason that becomes a public comment.
Source
Works?
no reports yet
Rating
◆
ATT&CK techniques
1Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.
▤ Build a SIEM detection for these techniques⬡
Weakness Classification
CWE-787Out-of-bounds Write
▤
Affected Products & Versions
36qualcomm msm8909w firmwareall versions
qualcomm msm8996au firmwareall versions
qualcomm qcs605 firmwareall versions
qualcomm 215 firmwareall versions
qualcomm sd 210 firmwareall versions
qualcomm sd 212 firmwareall versions
qualcomm sd 205 firmwareall versions
qualcomm sd 425 firmwareall versions
qualcomm sd 427 firmwareall versions
qualcomm sd 430 firmwareall versions
qualcomm sd 435 firmwareall versions
qualcomm sd 439 firmwareall versions
qualcomm sd 429 firmwareall versions
qualcomm sd 450 firmwareall versions
qualcomm sd 625 firmwareall versions
qualcomm sd 632 firmwareall versions
qualcomm sd 636 firmwareall versions
qualcomm sd 665 firmwareall versions
qualcomm sd 675 firmwareall versions
qualcomm sd 712 firmwareall versions
qualcomm sd 710 firmwareall versions
qualcomm sd 670 firmwareall versions
qualcomm sd 730 firmwareall versions
qualcomm sd 820 firmwareall versions
qualcomm sd 820a firmwareall versions
qualcomm sd 835 firmwareall versions
qualcomm sd 845 firmwareall versions
qualcomm sd 850 firmwareall versions
qualcomm sd 855 firmwareall versions
qualcomm sd 8cx firmwareall versions
qualcomm sda660 firmwareall versions
qualcomm sdm439 firmwareall versions
qualcomm sdm630 firmwareall versions
qualcomm sdm660 firmwareall versions
qualcomm snapdragon high med 2016 firmwareall versions
qualcomm sxr1130 firmwareall versions
▤
Related CVEs
8CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row.
CVE-2002-2227
Buffer underflow in ssldump 0.9b2 and earlier allows remote attackers to cause a...
same CWE-787
CVE-2003-0870
Heap-based buffer overflow in Opera 7.11 and 7.20 allows remote attackers to exe...
1
same CWE-787
CVE-2003-1396
Heap-based buffer overflow in Opera 6.05 through 7.10 allows remote attackers to...
1
same CWE-787
CVE-2004-0398
Heap-based buffer overflow in the ne_rfc1036_parse date parsing function for the...
same CWE-787
CVE-2014-10043
In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdra...
same product
HIGH
CVE-2014-10045
In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdra...
same product
CRITICAL
CVE-2014-10048
In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdra...
same product
CRITICAL
CVE-2014-10051
In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdra...
same product
CRITICAL
⚑
Vendor Advisories
1🔗
References & Sources
1Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.