# CVE-2024-2052: Path traversal in Easergy T200 (DNP3) Models: T200I, T200E, T200P, T200S, T200H

> An attacker can exfiltrate files and logs by modifying the download URL, affecting Schneider Electric Easergy T200 devices.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2024
- **Updated:** 15 Aug 2024
- **Also known as:** GHSA-p833-v842-wj4m

## What is CVE-2024-2052?

CVE-2024-2052 is a high-severity path traversal vulnerability in Schneider Electric Easergy T200 (DNP3) Models: T200I, T200E, T200P, T200S, T200H, published on 18 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CWE-552: Files or Directories Accessible to External Parties vulnerability exists that could allow
unauthenticated files and logs exfiltration and download of files when an attacker modifies the
URL to download to a different location.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

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


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

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

## Is CVE-2024-2052 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-2052 is a high-severity path traversal vulnerability in Schneider Electric Easergy T200 (DNP3) Models: T200I, T200E, T200P, T200S, T200H, published on 18 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-2052 in the wild and no public exploit code.

Affected product: Schneider Electric Easergy T200 (DNP3) Models: T200I, T200E, T200P, T200S, T200H. 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-2052/ (Markdown: https://insights.sbomify.com/CVE-2024-2052/index.md)
```

## Sources

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

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