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

> Attackers can bypass signature verification in the Google Play Services SDK on non-GMS devices by exploiting trust in debug versions.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Jul 2022
- **Updated:** 21 Apr 2025
- **Also known as:** GHSA-qfhf-vjgv-mm2w

## What is CVE-2022-1799?

CVE-2022-1799 is a medium-severity vulnerability in Google Play Services SDK, published on 29 Jul 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-501 (Trust Boundary Violation)

## Which versions are affected by CVE-2022-1799?

It affects 1 product.


Products: Google Google Play Services Software Development Kit.

## How do I fix CVE-2022-1799?

No fix has been published for CVE-2022-1799 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-1799 being exploited?

There is no known exploitation of CVE-2022-1799 in the wild and no public exploit code.

## Other vulnerabilities in Google Play Services SDK

- [CVE-2022-2390](https://insights.sbomify.com/CVE-2022-2390/): Mutable pending intent in Google Play services SDK (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1799 and fix it if it is affected.

What it is: CVE-2022-1799 is a medium-severity vulnerability in Google Play Services SDK, published on 29 Jul 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-1799 in the wild and no public exploit code.

Affected product: Google Play Services SDK. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-1799/ (Markdown: https://insights.sbomify.com/CVE-2022-1799/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-1799
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-1799
- OSV: https://osv.dev/vulnerability/CVE-2022-1799

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-1799/
Summaries are generated and may contain mistakes; the official description above is the record.