# CVE-2024-22063: ZTE ZENIC ONE R58 product has a CSV injection vulnerability

> An authenticated attacker can inject malicious code via CSV injection in ZTE ZENIC ONE R58 to tamper with messages and attack related devices.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Dec 2024
- **Updated:** 30 Dec 2024
- **Also known as:** GHSA-m7rr-9vhr-9v38

## What is CVE-2024-22063?

CVE-2024-22063 is a high-severity code injection vulnerability in ZTE ZENIC ONE R58, published on 30 Dec 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The ZENIC ONE R58 products by ZTE Corporation have a command injection vulnerability. An authenticated attacker can exploit this vulnerability to tamper with messages, inject malicious code, and subsequently launch attacks on related devices.

Weakness: CWE-1236 (Improper Neutralization of Formula Elements in a CSV File)

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

It affects 1 product.


Products: Zte Zenic One R58.

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

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

## Is CVE-2024-22063 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22063 is a high-severity code injection vulnerability in ZTE ZENIC ONE R58, published on 30 Dec 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-22063 in the wild and no public exploit code.

Affected product: ZTE ZENIC ONE R58. 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-22063/ (Markdown: https://insights.sbomify.com/CVE-2024-22063/index.md)
```

## Sources

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

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