dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2024-48442

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
Incorrect access control in Shenzhen Tuoshi Network Communications Co.,Ltd 5G CPE Router NR500-EA RG500UEAABxCOMSLICv3.2.2543.12.18 allows attackers to access the SSH protocol without authentication.

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 confidence

The Shenzhen Tuoshi Network Communications 5G CPE Router NR500-EA contains an incorrect access control vulnerability in firmware version v3.2.2543.12.18 that allows unauthenticated attackers to access the SSH service. This means the router's SSH daemon does not properly enforce authentication, enabling remote attackers to gain shell access without credentials.

MitigationApply the vendor firmware patch if available, or alternatively disable SSH access on the router if not required for management, and restrict network exposure through firewall rules or network segmentation to limit attack surface.

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the router's web interface or check the device label to confirm the model is NR500-EA from Shenzhen Tuoshi Network Communications
    Affected if The device is not the NR500-EA model, then this specific CVE does not apply
  2. Check the installed firmware version
    Log into the router's web administration panel and navigate to the Status or System Information page to view the firmware version. Alternatively, check via CLI if accessible.
    Affected if The firmware version matches v3.2.2543.12.18 or falls within the affected version range for this model, proceed to SSH checks
  3. Verify if SSH service is enabled
    In the router's web interface, go to the Security or Services settings and check if SSH server/daemon is turned ON. Look for settings named 'SSH', 'SSH Server', or 'Remote Management' that enable shell access.
    Affected if SSH service is enabled on the router, the device could be exploitable if network accessible
  4. Check SSH network exposure
    Review the router's firewall settings to determine if SSH port 22 is accessible from the WAN/internet side. Check port forwarding rules or DMZ settings that may expose SSH externally. Use an external port scanner from an untrusted network to confirm if port 22 responds.
    Affected if SSH port 22 is reachable from untrusted networks such as the WAN/internet, the device is vulnerable to unauthenticated remote access
  5. Confirm SSH accepts connections without credentials
    Attempt to connect to the router's SSH port (port 22) using an SSH client with any username and no password, or with test credentials. A successful connection without valid authentication confirms exploitation.
    Affected if SSH connection succeeds without valid credentials, the device is confirmed affected by this CVE

The device is affected if it is an NR500-EA router running firmware v3.2.2543.12.18 (or affected version) with SSH service enabled and accessible from untrusted networks, allowing remote unauthenticated shell access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor firmware patch if available, or alternatively disable SSH access on the router if not required for management, and restrict network exposure through firewall rules or network segmentation to limit attack surface.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-48442 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-48442 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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