# CVE-2024-28878: IOSIX IO-1020 Micro ELD Download of Code Without Integrity Check

> Attackers can execute arbitrary code on IOSiX IO-1020 Micro ELD devices by exploiting a lack of integrity checks during code downloads.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Apr 2024
- **Updated:** 26 Aug 2024
- **Also known as:** GHSA-vqqg-v6v5-gm7x

## What is CVE-2024-28878?

CVE-2024-28878 is a critical vulnerability in IOSiX IO-1020 Micro ELD, published on 12 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IO-1020 Micro ELD downloads source code or an executable from an 
adjacent location and executes the code without sufficiently verifying 
the origin or integrity of the code.

Weakness: CWE-494 (Download of Code Without Integrity Check)

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


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

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

## Is CVE-2024-28878 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-28878 is a critical vulnerability in IOSiX IO-1020 Micro ELD, published on 12 Apr 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-28878 in the wild and no public exploit code.

Affected product: IOSiX IO-1020 Micro ELD. 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-28878/ (Markdown: https://insights.sbomify.com/CVE-2024-28878/index.md)
```

## Sources

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

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