# CVE-2022-30339: Denial of service in Intel(R) Integrated Sensor Solution

> A privileged local attacker can cause a denial of service via an out-of-bounds read in Intel Integrated Sensor Solution firmware.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Feb 2023
- **Updated:** 27 Jan 2025
- **Also known as:** GHSA-6p5j-938v-6wm9

## What is CVE-2022-30339?

CVE-2022-30339 is a medium-severity denial of service vulnerability in Intel(R) Integrated Sensor Solution, published on 16 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Out-of-bounds read in firmware for the Intel(R) Integrated Sensor Solution before versions 5.4.2.4579v3, 5.4.1.4479 and 5.0.0.4143 may allow a privileged user to potentially enable denial of service via local access.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2022-30339?

It affects 1 product.


Products: Intel Integrated Sensor Solution.

## How do I fix CVE-2022-30339?

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

## Is CVE-2022-30339 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-30339 and fix it if it is affected.

What it is: CVE-2022-30339 is a medium-severity denial of service vulnerability in Intel(R) Integrated Sensor Solution, published on 16 Feb 2023. 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-2022-30339 in the wild and no public exploit code.

Affected product: Intel(R) Integrated Sensor Solution. 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-2022-30339/ (Markdown: https://insights.sbomify.com/CVE-2022-30339/index.md)
```

## Sources

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

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