# CVE-2024-8518: Denial of service in Zelio Soft 2

> Attackers can crash the Zelio Soft 2 application by tricking users into opening a specially crafted project file.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **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:** 8 Oct 2024
- **Updated:** 8 Oct 2024
- **Also known as:** GHSA-j6rp-5g87-ghhj

## What is CVE-2024-8518?

CVE-2024-8518 is a low-severity denial of service vulnerability in Schneider Electric Zelio Soft 2, published on 8 Oct 2024. 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

CWE-20: Improper Input Validation vulnerability exists that could cause a crash of the Zelio Soft
2 application when a specially crafted project file is loaded by an application user.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2024-8518 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8518 is a low-severity denial of service vulnerability in Schneider Electric Zelio Soft 2, published on 8 Oct 2024. 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-2024-8518 in the wild and no public exploit code.

Affected product: Schneider Electric Zelio Soft 2. 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-8518/ (Markdown: https://insights.sbomify.com/CVE-2024-8518/index.md)
```

## Sources

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

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