Security readout for executives and security teams
Plain-English summary
Some Android apps built with affected Google Play Services SDK could incorrectly trust a debug Google Play services build on non-GMS devices. That trust mistake can expose sensitive data or allow integrity impact, but high privileges and user interaction reduce broad exploitation likelihood.
Executive priority
Treat this as a moderate dependency remediation item. It can affect confidentiality and integrity, but available evidence does not show active exploitation and the attack conditions are restrictive. Patch through normal mobile release governance, prioritizing apps with non-GMS device exposure.
Technical view
CVE-2022-1799 is incorrect signature trust in Google Play services SDK play-services-basement. On non-GMS devices, the SDK may trust a debug version of Google Play services. CVSS 3.1 is 5.7 with high confidentiality and integrity impact, no availability impact, high attack complexity, high privileges, and required user interaction.
Likely exposure
Exposure is most likely in Android applications using Google Play Services SDK play-services-basement versions not upgraded past the May 3, 2022 release, especially where apps may run on non-GMS devices. The source bundle does not identify exact vulnerable version ranges.
Exploitation context
The source bundle does not report active exploitation, and this CVE is not listed as KEV. The CVSS vector suggests exploitation is constrained by high privileges, high complexity, and user interaction, so prioritize dependency hygiene over emergency incident response unless local evidence indicates abuse.
Researcher notes
Evidence is limited to the CVE description and Google release reference. Affected versions are unspecified, and no exploit details are provided. Validation should focus on dependency resolution, transitive inclusion of play-services-basement, and whether application trust decisions depend on Google Play services signatures on non-GMS devices.
Mitigation direction
- Upgrade Google Play Services SDK dependencies past the May 3, 2022 release.
- Confirm play-services-basement is not pinned to an older vulnerable dependency.
- Check Google release guidance for current recommended SDK versions.
- Prioritize apps distributed to or usable on non-GMS Android devices.
Validation and detection
- Inventory Android apps using Google Play Services SDK or play-services-basement.
- Review dependency manifests and build lockfiles for affected SDK versions.
- Confirm CI builds resolve to versions newer than the May 3, 2022 release.
- Assess whether supported device populations include non-GMS Android 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.
CWE-501: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-1799 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
- Medium
- CVSS
- 5.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N
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 vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N0.55.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.7MediumVector: CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://developers.google.com/android/guides/releases#may_03_2022CVE 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.
Trust Boundary Violation
Trust Boundary Violation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.