# CVE-2025-1143: Billion Electric M120N - Use of Hard-coded Credentials

> Attackers can use hard-coded SSH credentials to gain root access on Billion Electric routers, compromising the entire system.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2025
- **Updated:** 18 Feb 2025

## What is CVE-2025-1143?

CVE-2025-1143 is a high-severity vulnerability in Billion Electric M100, published on 11 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Certain models of routers from Billion Electric has hard-coded embedded linux credentials, allowing attackers to log in through the SSH service using these credentials and obtain root privilege of the system.

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

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


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

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

## Is CVE-2025-1143 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1143 is a high-severity vulnerability in Billion Electric M100, published on 11 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1143 in the wild and no public exploit code.

Affected product: Billion Electric M100. 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-1143/ (Markdown: https://insights.sbomify.com/CVE-2025-1143/index.md)
```

## Sources

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

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