# CVE-2024-22080: Memory corruption in n/a

> Unauthenticated attackers can trigger memory corruption via XML parsing, potentially leading to code execution or denial of service on Elspec G5 devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2024
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-676v-cr2h-h86m

## What is CVE-2024-22080?

CVE-2024-22080 is a critical memory corruption vulnerability in n/a, published on 20 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Elspec G5 digital fault recorder versions 1.1.4.15 and before. Unauthenticated memory corruption can occur during XML body parsing.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Elspec-Ltd G5dfr Firmware.

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

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

## Is CVE-2024-22080 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-22081](https://insights.sbomify.com/CVE-2024-22081/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-22078](https://insights.sbomify.com/CVE-2024-22078/): Privilege escalation in n/a (high 8.8)
- [CVE-2024-46601](https://insights.sbomify.com/CVE-2024-46601/): Memory corruption in n/a (high 7.5)
- [CVE-2024-46602](https://insights.sbomify.com/CVE-2024-46602/): XML external entity in n/a (high 7.5)
- [CVE-2024-46603](https://insights.sbomify.com/CVE-2024-46603/): XML external entity in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22080 is a critical memory corruption vulnerability in n/a, published on 20 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-22080 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-2024-22080/ (Markdown: https://insights.sbomify.com/CVE-2024-22080/index.md)
```

## Sources

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

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