# CVE-2023-35061: Information disclosure in Intel(R) PROSet/Wireless and Intel(R) Killer(TM) Wi-Fi software

> An unauthenticated attacker with adjacent access can potentially disclose information due to improper initialization in Intel Wi-Fi software.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Feb 2024
- **Updated:** 14 Aug 2024
- **Also known as:** DEBIAN-CVE-2023-35061, GHSA-wf2v-3pg9-p64x, UBUNTU-CVE-2023-35061

## What is CVE-2023-35061?

CVE-2023-35061 is a low-severity vulnerability in Intel(R) PROSet/Wireless and Intel(R) Killer(TM) Wi-Fi software, published on 14 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper initialization for the Intel(R) PROSet/Wireless and Intel(R) Killer(TM) Wi-Fi software before version 22.240 may allow an unauthenticated user to potentially enable information disclosure via adjacent access.

Weakness: CWE-665 (Improper Initialization)

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


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

Upgrade to a fixed version.

## Is CVE-2023-35061 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-35061 is a low-severity vulnerability in Intel(R) PROSet/Wireless and Intel(R) Killer(TM) Wi-Fi software, published on 14 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-35061 in the wild and no public exploit code.

Affected product: Intel(R) PROSet/Wireless and Intel(R) Killer(TM) Wi-Fi software. 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-35061/ (Markdown: https://insights.sbomify.com/CVE-2023-35061/index.md)
```

## Sources

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

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