# CVE-2023-52424: Security feature bypass in n/a

> Attackers can trick victims into connecting to untrusted networks by exploiting SSID confusion in Wi-Fi key derivation, bypassing network authentication protections.

- **Severity:** High 7.4 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 May 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-mh3c-527f-cwqv, MGASA-2024-0322, openSUSE-SU-2024:14338-1

## What is CVE-2023-52424?

CVE-2023-52424 is a high-severity vulnerability in n/a, published on 17 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The IEEE 802.11 standard sometimes enables an adversary to trick a victim into connecting to an unintended or untrusted network with Home WEP, Home WPA3 SAE-loop. Enterprise 802.1X/EAP, Mesh AMPE, or FILS, aka an "SSID Confusion" issue. This occurs because the SSID is not always used to derive the pairwise master key or session keys, and because there is not a protected exchange of an SSID during a 4-way handshake.

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

## Which versions are affected by CVE-2023-52424?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wpa_supplicant` | openSUSE:Tumbleweed | All versions | 2.11-1.1 |

## How do I fix CVE-2023-52424?

Apply the vendor's patch.

## Is CVE-2023-52424 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-52424 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-52424 and fix it if it is affected.

What it is: CVE-2023-52424 is a high-severity vulnerability in n/a, published on 17 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-52424 exists.

Affected product: n/a. 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-2023-52424/ (Markdown: https://insights.sbomify.com/CVE-2023-52424/index.md)
```

## Sources

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

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