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

> Attackers can log in as root using hardcoded credentials in the H3C Magic B1ST router firmware.

- **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 Aug 2024
- **Updated:** 17 Mar 2025
- **Also known as:** GHSA-f5hg-xwhp-3gj9

## What is CVE-2024-42638?

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

### Official description

H3C Magic B1ST v100R012 was discovered to contain a hardcoded password vulnerability in /etc/shadow, which allows attackers to log in as root.

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

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

It affects 1 product.


Products: H3c Magic B1st Firmware.

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

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

## Is CVE-2024-42638 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-34928](https://insights.sbomify.com/CVE-2023-34928/): Memory corruption in n/a (high 7.5)
- [CVE-2023-34929](https://insights.sbomify.com/CVE-2023-34929/): Memory corruption in n/a (high 7.5)
- [CVE-2023-34930](https://insights.sbomify.com/CVE-2023-34930/): Memory corruption in n/a (high 7.5)
- [CVE-2023-34931](https://insights.sbomify.com/CVE-2023-34931/): Memory corruption in n/a (high 7.5)
- [CVE-2023-34932](https://insights.sbomify.com/CVE-2023-34932/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-42638 is a critical vulnerability in n/a, published on 16 Aug 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-42638 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-42638/ (Markdown: https://insights.sbomify.com/CVE-2024-42638/index.md)
```

## Sources

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

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