# CVE-2024-9005: Deserialization in EcoStruxure Power Monitoring Expert (PME)

> Remote attackers can execute arbitrary code on Schneider Electric EcoStruxure Power Monitoring Expert servers by sending maliciously serialized data.

- **Severity:** High 7.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Oct 2024
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-h25j-66v8-m35v

## What is CVE-2024-9005?

CVE-2024-9005 is a high-severity unsafe deserialization vulnerability in Schneider Electric EcoStruxure Power Monitoring Expert (PME), published on 8 Oct 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

CWE-502: Deserialization of Untrusted Data vulnerability exists that could allow code to be
remotely executed on the server when unsafely deserialized data is posted to the web server.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2024-9005 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-9005 is a high-severity unsafe deserialization vulnerability in Schneider Electric EcoStruxure Power Monitoring Expert (PME), published on 8 Oct 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-9005 in the wild and no public exploit code.

Affected product: Schneider Electric EcoStruxure Power Monitoring Expert (PME). 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-9005/ (Markdown: https://insights.sbomify.com/CVE-2024-9005/index.md)
```

## Sources

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

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