CVE-2025-43982
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 · uneditedShenzhen Tuoshi NR500-EA RG500UEAABxCOMSLICv3.4.2731.16.43 devices enable the SSH service by default. There is a hidden hard-coded root account that cannot be disabled in the GUI.
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 confidenceThe Shenzhen Tuoshi NR500-EA RG500UEAABxCOMSLICv3.4.2731.16.43 cellular router devices have SSH service enabled by default with a hidden hard-coded root account that cannot be disabled through the web GUI. This allows unauthenticated remote attackers to gain full root access to the device.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 device model and firmware versionAccess the device web GUI (typically at 192.168.1.1 or similar) and navigate to the Status or System Information page to find the exact model number and firmware version. Alternatively, check physical device labels.Affected if The device model is Shenzhen Tuoshi NR500-EA or RG500UEAABxCOMSLICv3.4.2731.16.43, or the firmware version matches or is within the v3.4.2731.16.43 series.
-
Verify SSH service is enabledAttempt to connect to the device on port 22 using an SSH client (e.g., 'nc -zv <device_ip> 22' or 'nmap -p 22 <device_ip>'). If the connection succeeds, SSH is active.Affected if SSH port 22 responds and accepts connections, indicating the SSH service is enabled on the device.
-
Check SSH access from the web GUILog into the device web GUI and navigate to Network Settings, Services, or Security sections to locate SSH configuration. Verify whether there is an option to enable/disable SSH and whether it is currently enabled.Affected if The SSH service is enabled in the web GUI configuration and is accessible externally or on the expected network interface.
-
Confirm hard-coded root account cannot be disabledIn the web GUI, locate any user management or SSH settings. Attempt to disable or remove any root or admin account options. Observe if the hard-coded root account persists despite attempts to disable or remove it through the GUI.Affected if The web GUI shows a root or admin account that cannot be disabled, removed, or whose settings revert, indicating a non-configurable hard-coded account is present.
The device is affected if it is a Shenzhen Tuoshi NR500-EA or RG500UEAABxCOMSLICv3.4.2731.16.43 model with SSH enabled and a root account that cannot be disabled through the web interface.
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 dataDisable the SSH service if not required, or implement strict network access controls to limit SSH access to trusted IP addresses only. Contact the vendor for a firmware update that removes the hard-coded credentials.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43982 — 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-43982 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