# CVE-2023-33105: Configuration Issue in WLAN Host and Firmware

> An attacker can cause a transient denial of service in Qualcomm Snapdragon WLAN firmware by sending numerous invalid authentication frames.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Mar 2024
- **Updated:** 26 Aug 2024
- **Also known as:** GHSA-hfr9-gm39-p2g7

## What is CVE-2023-33105?

CVE-2023-33105 is a high-severity denial of service vulnerability in Qualcomm Ar8035 Firmware, published on 4 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Transient DOS in WLAN Host and Firmware when large number of open authentication frames are sent with an invalid transaction sequence number.

Weakness: CWE-16

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

It affects 149 products.


Products: Qualcomm Ar8035 Firmware, Qualcomm Ar9380 Firmware, Qualcomm Csr8811 Firmware, Qualcomm Fastconnect 6700 Firmware, Qualcomm Fastconnect 6900 Firmware, Qualcomm Fastconnect 7800 Firmware, Qualcomm Flight Rb5 5g Firmware, Qualcomm Immersive Home 214 Firmware, Qualcomm Immersive Home 216 Firmware, Qualcomm Immersive Home 316 Firmware, Qualcomm Immersive Home 318 Firmware, Qualcomm Immersive Home 3210 Firmware, Qualcomm Immersive Home 326 Firmware, Qualcomm Ipq4018 Firmware, Qualcomm Ipq4019 Firmware, Qualcomm Ipq4028 Firmware, Qualcomm Ipq4029 Firmware, Qualcomm Ipq5010 Firmware, Qualcomm Ipq5028 Firmware, Qualcomm Ipq5302 Firmware and 129 more.

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

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

## Is CVE-2023-33105 being exploited?

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

Public exploit code:

- This repository contains the exploit code for CVE-2023-33105, a vulnerability identified in Qualcomm devices. The exploit leverages authentication frames to perform a denial of service (DoS) attack on a target access point (AP) by sending a large number of open authentication frames with an invalid transaction sequence number. (github_poc): https://github.com/D3adP3nguin/CVE-2023-33105-Transient-DOS-in-WLAN-Host-and-Firmware

## Other vulnerabilities in Qualcomm Ar8035 Firmware

- [CVE-2023-33106](https://insights.sbomify.com/CVE-2023-33106/): Qualcomm Multiple Chipsets Use of Out-of-Range Pointer Offset (high 8.4, exploited in the wild)
- [CVE-2024-45569](https://insights.sbomify.com/CVE-2024-45569/): Improper Validation of Array Index in WLAN Host Communication (critical 9.8)
- [CVE-2024-21473](https://insights.sbomify.com/CVE-2024-21473/): Improper Input Validation in WIN SON (critical 9.8)
- [CVE-2023-28582](https://insights.sbomify.com/CVE-2023-28582/): Buffer Copy Without Checking Size of Input in Data Modem (critical 9.8)
- [CVE-2023-43552](https://insights.sbomify.com/CVE-2023-43552/): Use After Free in WLAN Host Communication (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-33105 is a high-severity denial of service vulnerability in Qualcomm Ar8035 Firmware, published on 4 Mar 2024. 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-2023-33105 in the wild and no public exploit code.

Affected product: Qualcomm Ar8035 Firmware. 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-33105/ (Markdown: https://insights.sbomify.com/CVE-2023-33105/index.md)
```

## Sources

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

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