# CVE-2024-2051: Auth bypass in Easergy T200 (DNP3) Models: T200I, T200E, T200P, T200S, T200H

> Attackers can take over accounts and gain unauthorized access via brute-force attacks on the login form due to missing rate limiting.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 18 Mar 2024
- **Updated:** 28 Aug 2024
- **Also known as:** GHSA-jvxm-6mgq-929w

## What is CVE-2024-2051?

CVE-2024-2051 is a critical authentication bypass 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-307: Improper Restriction of Excessive Authentication Attempts vulnerability exists that
could cause account takeover and unauthorized access to the system when an attacker
conducts brute-force attacks against the login form.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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


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

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

## Is CVE-2024-2051 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-2051 is a critical authentication bypass 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-2051 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-2051/ (Markdown: https://insights.sbomify.com/CVE-2024-2051/index.md)
```

## Sources

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

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