CVE-2017-18125
Last modified
CVE-2017-18125 is a vulnerability of currently unknown severity. In Android before security patch level 2018-04-05 on Qualcomm Snapdragon Mobile and Snapdragon Wear MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 835, SD 845, SD 850, when secure camera is activated it stores captured data in protected buffers. The TEE application which uses secure camera expects those buffers to contain data captured during the current camera session. EPSS estimates a 0.67% chance of exploitation in the next 30 days.
Description
In Android before security patch level 2018-04-05 on Qualcomm Snapdragon Mobile and Snapdragon Wear MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 835, SD 845, SD 850, when secure camera is activated it stores captured data in protected buffers. The TEE application which uses secure camera expects those buffers to contain data captured during the current camera session. It is possible though for HLOS to put aside and reuse one or more of the protected buffers with previously captured data during next camera session. Such data reuse must be prevented as the TEE applications expects to receive valid data captured during the current session only.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Qualcomm | Mdm9206 Firmware | All versions |
| Qualcomm | Mdm9607 Firmware | All versions |
| Qualcomm | Mdm9650 Firmware | All versions |
| Qualcomm | Sd 210 Firmware | All versions |
| Qualcomm | Sd 212 Firmware | All versions |
| Qualcomm | Sd 205 Firmware | All versions |
| Qualcomm | Sd 835 Firmware | All versions |
| Qualcomm | Sd 845 Firmware | All versions |
| Qualcomm | Sd 850 Firmware | All versions |
References
- http://www.securityfocus.com/bid/103671Third Party Advisory, VDB Entry
- https://source.android.com/security/bulletin/2018-04-01Vendor Advisory
- http://www.securityfocus.com/bid/103671Third Party Advisory, VDB Entry
- https://source.android.com/security/bulletin/2018-04-01Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-18125?
How severe is CVE-2017-18125?
How do I fix CVE-2017-18125?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-1812Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultI…
- CVE-2017-18120A double-free bug in the read_gif function in gifread.c in g…
- CVE-2017-18121The consentAdmin module in SimpleSAMLphp through 1.14.15 is …
- CVE-2017-18122A signature-validation bypass issue was discovered in Simple…
- CVE-2017-18123The call parameter of /lib/exe/ajax.php in DokuWiki through …
- CVE-2017-18124During secure boot, addition is performed on uint8 ptrs whic…
- CVE-2017-18126In Android before security patch level 2018-04-05 on Qualcom…
- CVE-2017-18127In Android before security patch level 2018-04-05 on Qualcom…
- CVE-2017-18128In Android before security patch level 2018-04-05 on Qualcom…
- CVE-2017-18129In Android before security patch level 2018-04-05 on Qualcom…
- CVE-2017-1813Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultI…
- CVE-2017-18130In Android before security patch level 2018-04-05 on Qualcom…
Are you affected by CVE-2017-18125?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST