Security readout for executives and security teams
Plain-English summary
This CVE describes a Leagoo P1 Android firmware issue where any app on the device can trigger screenshots through modified Android framework code. Screenshots may capture sensitive notification content, including one-time passcodes. The sources do not identify a patch, CVSS score, or active exploitation.
Executive priority
Treat this as a targeted mobile fleet risk, not an internet-wide emergency. Prioritize confirmation of affected devices and remove them from sensitive use if present.
Technical view
The described Leagoo P1 build modifies the Android system_server process in the core android package. An exported broadcast receiver allows co-located apps to initiate screenshots and write them to external storage. With status-bar expansion, notification content may be exposed even when the screen is locked.
Likely exposure
Exposure appears limited to Leagoo P1 devices matching the cited Android 6.0 build fingerprint. Fleet exposure depends on whether those exact devices or firmware builds are present.
Exploitation context
The public sources describe local app-based abuse, not remote compromise. CISA KEV is false, and the provided sources do not report active exploitation in the wild.
Researcher notes
Evidence is specific but incomplete. The sources describe the vulnerable behavior and firmware fingerprint, but provide no CVSS, patch status, broad affected-version list, or exploitation evidence.
Mitigation direction
- Check Leagoo or firmware vendor guidance for any fixed firmware.
- Inventory devices for the exact Leagoo P1 build fingerprint.
- Remove matching devices from sensitive workflows until remediated.
- Restrict app installation to trusted, managed applications.
- Reduce sensitive content shown in lock-screen notifications.
Validation and detection
- Confirm whether any managed device matches the cited build fingerprint.
- Review mobile asset inventory for Leagoo P1 devices.
- Check vendor and firmware channels for remediation status.
- Review installed apps on matching devices for unmanaged software.
- Assess whether SMS or notification OTPs are used on matching devices.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2018-14997 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.kryptowire.com/portal/wp-content/uploads/2018/12/DEFCON-26-Johnson-and-Stavrou-Vulnerable-Out-of-the-Box-An-Eval-of-Android-Carrier-Devices-WP-Updated.pdfCVE reference · x_refsource_MISC
- https://www.kryptowire.com/portal/android-firmware-defcon-2018/CVE reference · x_refsource_MISC
- https://www.kryptowire.com/CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.