# CVE-2023-29474: Command injection in n/a

> Unauthenticated attackers can execute arbitrary commands and gain administrative access on Atos Unify OpenScape 4000 platforms.

- **Severity:** Critical 9.8 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Apr 2023
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-m76f-5v6g-6jmr

## What is CVE-2023-29474?

CVE-2023-29474 is a critical command injection vulnerability in n/a, published on 6 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

inventory in Atos Unify OpenScape 4000 Platform and OpenScape 4000 Manager Platform 10 R1 before 10 R1.34.4 allows an unauthenticated attacker to run arbitrary commands on the platform operating system and achieve administrative access, aka OSFOURK-23552.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2023-29474?

It affects 2 products.


Products: Atos Unify Openscape 4000, Atos Unify Openscape 4000 Manager.

## How do I fix CVE-2023-29474?

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

## Is CVE-2023-29474 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-29473](https://insights.sbomify.com/CVE-2023-29473/): Command injection in n/a (critical 9.8)
- [CVE-2023-29475](https://insights.sbomify.com/CVE-2023-29475/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-29474 and fix it if it is affected.

What it is: CVE-2023-29474 is a critical command injection vulnerability in n/a, published on 6 Apr 2023. 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-2023-29474 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-2023-29474/ (Markdown: https://insights.sbomify.com/CVE-2023-29474/index.md)
```

## Sources

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

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