# CVE-2024-6654: Denial of Service vulnerability in ESET products for macOS

> A local attacker can cause a denial of service, disabling ESET security protection and slowing down the macOS system.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **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:** 27 Sep 2024
- **Updated:** 9 Oct 2024
- **Also known as:** GHSA-8v4g-x6m4-p3qj

## What is CVE-2024-6654?

CVE-2024-6654 is a medium-severity denial of service vulnerability in ESET, spol. s r.o. ESET Cyber Security, published on 27 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Products for macOS enables a user logged on to the system to perform a denial-of-service attack, which could be misused to disable the protection of the ESET security product and cause general system slow-down.

Weakness: CWE-377 (DEPRECATED: Insecure Temporary File)

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


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

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

## Is CVE-2024-6654 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6654 is a medium-severity denial of service vulnerability in ESET, spol. s r.o. ESET Cyber Security, published on 27 Sep 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-2024-6654 in the wild and no public exploit code.

Affected product: ESET, spol. s r.o. ESET Cyber Security. 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-6654/ (Markdown: https://insights.sbomify.com/CVE-2024-6654/index.md)
```

## Sources

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

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