# CVE-2024-45370: Auth bypass in Easy Config System

> An attacker can bypass authentication in Socomec Easy Config System by modifying a local database record to gain unauthorized access.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N`)
- **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:** 1 Dec 2025
- **Updated:** 1 Dec 2025
- **Also known as:** GHSA-rf5q-gfcj-2hp3

## What is CVE-2024-45370?

CVE-2024-45370 is a high-severity authentication bypass vulnerability in Socomec Easy Config System, published on 1 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An authentication bypass vulnerability exists in the User profile management functionality of Socomec Easy Config System 2.6.1.0. A specially crafted database record can lead to unauthorized access. An attacker can modify a local database to trigger this vulnerability.

Weakness: CWE-302 (Authentication Bypass by Assumed-Immutable Data)

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


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

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

## Is CVE-2024-45370 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45370 is a high-severity authentication bypass vulnerability in Socomec Easy Config System, published on 1 Dec 2025. 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-45370 in the wild and no public exploit code.

Affected product: Socomec Easy Config System. 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-45370/ (Markdown: https://insights.sbomify.com/CVE-2024-45370/index.md)
```

## Sources

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

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