# CVE-2024-36080: Hardcoded credentials in n/a

> Westermo EDW-100 devices contain a hidden root account with an unchangeable hardcoded password, allowing attackers to gain full administrative control.

- **Severity:** Critical 9.8 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 May 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-r73q-v44r-mw6r

## What is CVE-2024-36080?

CVE-2024-36080 is a critical vulnerability in n/a, published on 19 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Westermo EDW-100 devices through 2024-05-03 have a hidden root user account with a hardcoded password that cannot be changed. NOTE: this is a serial-to-Ethernet converter that should not be placed at the edge of the network.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2024-36080 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-36080 is a critical vulnerability in n/a, published on 19 May 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-36080 in the wild and no public exploit code.

Affected product: n/a. 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-36080/ (Markdown: https://insights.sbomify.com/CVE-2024-36080/index.md)
```

## Sources

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

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