# CVE-2024-2747: Privilege escalation in Easergy Studio

> A local attacker can escalate privileges by replacing a trusted file in an unquoted search path, requiring a system reboot to execute malicious code.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2024
- **Updated:** 19 Aug 2024
- **Also known as:** GHSA-qhx6-9fwx-wcfm

## What is CVE-2024-2747?

CVE-2024-2747 is a high-severity vulnerability in Schneider Electric Easergy Studio, published on 12 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

CWE-428: Unquoted search path or element vulnerability exists in Easergy Studio, which could
cause privilege escalation when a valid user replaces a trusted file name on the system and
reboots the machine.

Weakness: CWE-428 (Unquoted Search Path or Element)

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

It affects 1 product.


Products: Schneider-Electric Easergy Studio.

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

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

## Is CVE-2024-2747 being exploited?

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

## Other vulnerabilities in Schneider Electric Easergy Studio

- [CVE-2023-7032](https://insights.sbomify.com/CVE-2023-7032/): Deserialization in Easergy Studio (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-2747 is a high-severity vulnerability in Schneider Electric Easergy Studio, published on 12 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-2747 in the wild and no public exploit code.

Affected product: Schneider Electric Easergy Studio. 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-2747/ (Markdown: https://insights.sbomify.com/CVE-2024-2747/index.md)
```

## Sources

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

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