# CVE-2024-41975: CODESYS (Edge) Gateway for Windows insecure default

> Unauthenticated attackers can access limited PLC network information via insecure defaults in CODESYS Edge Gateway for Windows.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 2025
- **Updated:** 18 Mar 2025
- **Also known as:** GHSA-f9hf-p7m4-xh2g

## What is CVE-2024-41975?

CVE-2024-41975 is a medium-severity vulnerability in CODESYS Edge Gateway, published on 18 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated remote attacker can gain limited information of the PLC network but the user management of the PLCs prevents the actual access to the PLCs.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

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


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

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

## Is CVE-2024-41975 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-41975 is a medium-severity vulnerability in CODESYS Edge Gateway, published on 18 Mar 2025. 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-41975 in the wild and no public exploit code.

Affected product: CODESYS Edge Gateway. 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-41975/ (Markdown: https://insights.sbomify.com/CVE-2024-41975/index.md)
```

## Sources

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

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