# CVE-2024-8258: Insecure Electron Fuses in Logitech Options Plus Allowing Arbitrary Code Execution on macOS

> Attackers can execute arbitrary code on macOS via insecure Electron Fuses configuration in Logitech Options Plus.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:L/SA:L/AU:Y/R:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2024
- **Updated:** 10 Sep 2024
- **Also known as:** GHSA-5hm7-x82q-99rh

## What is CVE-2024-8258?

CVE-2024-8258 is a low-severity code injection vulnerability in Logitech Options Plus, published on 10 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper Control of Generation of Code ('Code Injection') in Electron Fuses in Logitech Options Plus version 1.60.496306 on macOS allows attackers to execute arbitrary code via insecure Electron Fuses configuration.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2024-8258?

It affects 1 product.


Products: Logitech Logi Options\+.

## How do I fix CVE-2024-8258?

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

## Is CVE-2024-8258 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8258 and fix it if it is affected.

What it is: CVE-2024-8258 is a low-severity code injection vulnerability in Logitech Options Plus, published on 10 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-8258 exists.

Affected product: Logitech Options Plus. 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-2024-8258/ (Markdown: https://insights.sbomify.com/CVE-2024-8258/index.md)
```

## Sources

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

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