# CVE-2025-61330: Hardcoded credentials in n/a

> Attackers can gain root access to H3C Magic devices via Telnet using hard-coded weak passwords, potentially leading to full device compromise.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:** 16 Oct 2025
- **Updated:** 16 Oct 2025
- **Also known as:** GHSA-62cf-rj26-wc9v

## What is CVE-2025-61330?

CVE-2025-61330 is a medium-severity vulnerability in n/a, published on 16 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A hard-coded weak password vulnerability has been discovered in all Magic-branded devices from Chinese network equipment manufacturer H3C. The vulnerability stems from the use of a hard-coded weak password for the root account in the /etc/shadow configuration or even the absence of any password at all. Some of these devices have the Telnet service enabled by default, or users can choose to enable the Telnet service in other device management interfaces (e.g. /debug.asp or /debug_telnet.asp). In addition, these devices have related interfaces called Virtual Servers, which can map the devices to the public network, posing the risk of remote attacks. Therefore, attackers can obtain the highest root privileges of the devices through the Telnet service using the weak password hardcoded in the firmware (or without a password), and remote attacks are possible.

Weakness: CWE-259 (Use of Hard-coded Password)

## Which versions are affected by CVE-2025-61330?


## How do I fix CVE-2025-61330?

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

## Is CVE-2025-61330 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-61330 and fix it if it is affected.

What it is: CVE-2025-61330 is a medium-severity vulnerability in n/a, published on 16 Oct 2025. 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-2025-61330 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-2025-61330/ (Markdown: https://insights.sbomify.com/CVE-2025-61330/index.md)
```

## Sources

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

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