# CVE-2024-32918: Permission Bypass allowing attackers to disable HDCP 2.2 encryption by not completing the HDCP Key Exchange initialization steps


- **Severity:** Medium 6.1 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 13 Jun 2024
- **Updated:** 19 Aug 2024
- **Also known as:** A-327233647, GHSA-p6jh-36mx-hrg4, PUB-A-327233647

## What is CVE-2024-32918?

CVE-2024-32918 is a medium-severity vulnerability in Google Android, published on 13 Jun 2024. 

### Official description

Permission Bypass allowing attackers  to disable HDCP 2.2 encryption by not completing the HDCP Key Exchange initialization steps

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2024-32918?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2024-32918?

Upgrade to a fixed version.

## Is CVE-2024-32918 being exploited?

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

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-32918 and fix it if it is affected.

What it is: CVE-2024-32918 is a medium-severity vulnerability in Google Android, published on 13 Jun 2024. 
Exploitation: There is no known exploitation of CVE-2024-32918 in the wild and no public exploit code.

Affected product: Google Android. 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-2024-32918/ (Markdown: https://insights.sbomify.com/CVE-2024-32918/index.md)
```

## Sources

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

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