CVE-2025-1143
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCertain 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCertain Billion Electric router models contain hard-coded embedded Linux credentials baked into the firmware. Attackers can authenticate to the SSH service using these credentials and obtain root system privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Billion Electric router modelCheck the device model number via web interface, router status page, or by examining the device label. Also check the DHCP lease table or network devices list for manufacturer identifier 'Billion'.Affected if The device is a Billion Electric router and SSH service is exposed.
-
Verify SSH service statusRun 'netstat -tuln | grep :22' or 'ss -tuln | grep :22' to check if port 22 (SSH) is listening. Alternatively, attempt an outbound connection to the device's SSH port from a trusted host.Affected if SSH service is enabled and accessible on the device.
-
Check for unauthorized root accessExamine /var/log/secure, /var/log/auth.log, or equivalent logs on the device (if accessible via console or diagnostic interface) for successful SSH login attempts. Also check 'last' command output for any unexpected root logins.Affected if There are SSH login logs from unknown sources or unexpected root session records.
-
Review SSH authentication logsIf you have diagnostic access, grep the system logs for 'sshd' authentication events, particularly looking for logins occurring outside of administrative windows or from unexpected IP addresses.Affected if SSH authentication attempts have succeeded from untrusted or unknown IP addresses.
-
Check for root privilege escalation indicatorsReview /var/log/sudo.log if available, check for any new sudoers configurations, and examine /root/.bash_history for unexpected commands. Look for indicators of privilege escalation such as 'su -' or 'sudo su' commands from non-administrator accounts.Affected if Root escalation has occurred - new accounts added, sudo configuration modified, or root shells obtained via SSH.
A defender is affected if they operate a Billion Electric router with SSH exposed, and evidence exists of unauthorized SSH access or root privilege escalation from external authentication attempts.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor firmware updates if available that remove hard-coded credentials; otherwise replace affected router models with those supporting proper credential management and secure authentication.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1143 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-1143 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data