# CVE-2024-20153: Other in MT2737, MT6989, MT6991, MT7925, MT8365, MT8518S, MT8532, MT8666, MT8667, MT8673, MT8676, MT8678, MT8755, MT8766, MT8768, MT8775, MT8781, MT8786, MT8788, MT8796, MT8798, MT8893

> Attackers can trick clients into connecting to spoofed access points, leading to remote information disclosure without user interaction.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jan 2025
- **Updated:** 6 Jan 2025
- **Also known as:** GHSA-2h9f-xm25-q379

## What is CVE-2024-20153?

CVE-2024-20153 is a high-severity vulnerability in Google Android, published on 6 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In wlan STA, there is a possible way to trick a client to connect to an AP with spoofed SSID. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS08990446 / ALPS09057442; Issue ID: MSV-1598.

Weakness: CWE-304 (Missing Critical Step in Authentication)

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

It affects 3 products.


Products: Google Android, Linuxfoundation Yocto, Mediatek Software Development Kit.

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

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

## Is CVE-2024-20153 being exploited?

There is no known exploitation of CVE-2024-20153 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-20153 and fix it if it is affected.

What it is: CVE-2024-20153 is a high-severity vulnerability in Google Android, published on 6 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-20153 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-20153/ (Markdown: https://insights.sbomify.com/CVE-2024-20153/index.md)
```

## Sources

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

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