# CVE-2024-8531: Code injection in Data Center Expert

> Attackers can execute arbitrary bash scripts as root by manipulating upgrade bundles in Schneider Electric Data Center Expert software.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2024
- **Updated:** 15 Oct 2024
- **Also known as:** GHSA-53j3-c5gj-9m5j

## What is CVE-2024-8531?

CVE-2024-8531 is a high-severity code injection vulnerability in Schneider Electric Data Center Expert, published on 11 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

CWE-347: Improper Verification of Cryptographic Signature vulnerability exists that could
compromise the Data Center Expert software when an upgrade bundle is manipulated to
include arbitrary bash scripts that are executed as root.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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


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

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

## Is CVE-2024-8531 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8531 is a high-severity code injection vulnerability in Schneider Electric Data Center Expert, published on 11 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-8531 in the wild and no public exploit code.

Affected product: Schneider Electric Data Center Expert. 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-8531/ (Markdown: https://insights.sbomify.com/CVE-2024-8531/index.md)
```

## Sources

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

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