# CVE-2022-34108: Denial of service in n/a

> Attackers can cause a Denial of Service in MSI Feature Navigator by providing a crafted image or video file.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Sep 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-mjmc-34rr-8mwh

## What is CVE-2022-34108?

CVE-2022-34108 is a high-severity denial of service vulnerability in n/a, published on 12 Sep 2022. 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

An issue in the Feature Navigator of Micro-Star International MSI Feature Nagivator v1.0.1808.0901 allows attackers to cause a Denial of Service (DoS) via a crafted image or video file.

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

It affects 1 product.


Products: Msi Micro-Star International Feature Navigator.

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

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

## Is CVE-2022-34108 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-34109](https://insights.sbomify.com/CVE-2022-34109/): File upload in n/a (high 7.1)
- [CVE-2022-34110](https://insights.sbomify.com/CVE-2022-34110/): Path traversal in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-34108 is a high-severity denial of service vulnerability in n/a, published on 12 Sep 2022. 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: There is no known exploitation of CVE-2022-34108 in the wild and no public exploit code.

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-2022-34108/ (Markdown: https://insights.sbomify.com/CVE-2022-34108/index.md)
```

## Sources

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

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