# CVE-2023-42336: Hardcoded credentials in n/a

> A remote attacker can execute arbitrary code and access sensitive information by exploiting hardcoded credentials in the password parameter of the NETIS WF2409Ev4 router.

- **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:** 16 Sep 2023
- **Updated:** 25 Sep 2024
- **Also known as:** GHSA-ch56-5g7c-36xc

## What is CVE-2023-42336?

CVE-2023-42336 is a critical vulnerability in n/a, published on 16 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in NETIS SYSTEMS WF2409Ev4 v.1.0.1.705 allows a remote attacker to execute arbitrary code and obtain sensitive information via the password parameter in the /etc/shadow.sample component.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2023-42336?

It affects 1 product.


Products: Netis-Systems Wf2409e Firmware.

## How do I fix CVE-2023-42336?

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

## Is CVE-2023-42336 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-42336 exists.

## Other vulnerabilities in n/a

- [CVE-2023-38829](https://insights.sbomify.com/CVE-2023-38829/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-42336 and fix it if it is affected.

What it is: CVE-2023-42336 is a critical vulnerability in n/a, published on 16 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-42336 exists.

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-2023-42336/ (Markdown: https://insights.sbomify.com/CVE-2023-42336/index.md)
```

## Sources

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

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