An integer underflow may occur due to lack of check when received data length from font_mgr_qsee_request_service is bigger than the minimal
An integer underflow may occur due to lack of check when received data length from font_mgr_qsee_request_service is bigger than the minimal value of the segment header, which may result in a buffer overflow, in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear in MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 820, SD 820A, SD 835, SD 845, SD 850.
- Published
- May 6, 2019
- Updated
- Jun 16, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- CWE-191
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
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
| Vendor | Product | CPE |
|---|---|---|
| qualcomm | mdm9206 firmware | cpe:2.3:o:qualcomm:mdm9206_firmware |
| qualcomm | mdm9206 | cpe:2.3:h:qualcomm:mdm9206 |
| qualcomm | mdm9607 firmware | cpe:2.3:o:qualcomm:mdm9607_firmware |
| qualcomm | mdm9607 | cpe:2.3:h:qualcomm:mdm9607 |
| qualcomm | mdm9650 firmware | cpe:2.3:o:qualcomm:mdm9650_firmware |
| qualcomm | mdm9650 | cpe:2.3:h:qualcomm:mdm9650 |
| 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 |
and 22 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm mdm9206 firmwareall versions
- qualcomm mdm9607 firmwareall versions
- qualcomm mdm9650 firmwareall versions
- qualcomm sd 205 firmwareall versions
- qualcomm sd 210 firmwareall versions
- qualcomm sd 212 firmwareall versions
- qualcomm sd 425 firmwareall versions
- qualcomm sd 430 firmwareall versions
- qualcomm sd 450 firmwareall versions
- qualcomm sd 625 firmwareall versions
- qualcomm sd 650 firmwareall versions
- qualcomm sd 652 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
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 Technologies, Inc. Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear
- MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 820, SD 820A, SD 835 … (+2)affected
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-14913In Android before 2018-01-05 on Qualcomm Snapdragon IoT, Snapdragon Mobile MDM9206, SD 625, SD 650/52, SD 835, SD 845, DDR address input val40Plan
- CVE-2017-14911In Android before 2018-01-05 on Qualcomm Snapdragon IoT, Snapdragon Mobile, Snapdragon Automobile APQ8096AU, MDM9206, MDM9650, MSM8996AU, SD40Plan
- CVE-2019-10541Dereference on uninitialized buffer can happen when parsing FLV clip with corrupted codec specific data in Snapdragon Auto, Snapdragon Compu39Monitor
- CVE-2019-10534Null-pointer dereference can occur while accessing the super index entry when it is not been allocated in Snapdragon Auto, Snapdragon Comput39Monitor
- CVE-2019-10533Out of bound access due to improper validation of array index cause the index table entry to get corrupt in Snapdragon Auto, Snapdragon Comp39Monitor
- CVE-2019-10528Use after free issue in kernel while accessing freed mdlog session info and its attributes after closing the session in Snapdragon Auto, Sna39Monitor
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.
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.
Credits
All researchersFinders, 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
Weakness class (CWE)
CWE-191 · Integer Underflow (Wrap or Wraparound)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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
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 helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.