# CVE-2024-1624: Command injection in Documentation server

> Attackers can execute arbitrary OS commands via crafted HTTP requests to the documentation server in affected Dassault Systèmes products.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 1 Mar 2024
- **Updated:** 28 Aug 2024
- **Also known as:** GHSA-g8fm-5mh4-g978

## What is CVE-2024-1624?

CVE-2024-1624 is a critical command injection vulnerability in Dassault Systèmes Documentation server, published on 1 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An OS Command Injection vulnerability affecting documentation server on 3DEXPERIENCE from Release 3DEXPERIENCE R2022x through Release 3DEXPERIENCE R2024x, SIMULIA Abaqus from Release 2022 through Release 2024, SIMULIA Isight from Release 2022 through Release 2024 and CATIA Composer from Release R2023 through Release R2024. A specially crafted HTTP request can lead to arbitrary command execution.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2024-1624 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1624 is a critical command injection vulnerability in Dassault Systèmes Documentation server, published on 1 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-1624 in the wild and no public exploit code.

Affected product: Dassault Systèmes Documentation server. 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-1624/ (Markdown: https://insights.sbomify.com/CVE-2024-1624/index.md)
```

## Sources

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

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