dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-37855

HIGH · 8.4 CVSS v3.1 Published 2024-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
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
An issue in Nepstech Wifi Router xpon (terminal) NTPL-Xpon1GFEVN, hardware verstion 1.0 firmware 2.0.1 allows a remote attacker to execute arbitrary code via the router's Telnet port 2345 without requiring authentication credentials.

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

Pre-authentication remote code execution vulnerability in Nepstech Wifi Router xpon NTPL-Xpon1GFEVN (firmware 2.0.1). An unauthenticated remote attacker can send arbitrary commands through Telnet service on port 2345, achieving full system compromise without any credentials.

MitigationImmediately restrict network access to port 2345 via firewall rules or disable the Telnet service if unused. Contact vendor for firmware update; if unavailable, consider network segmentation or device replacement.

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 checks

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

  1. Identify the device model
    Log into the router admin interface or check the device label/packaging for model number 'NTPL-Xpon1GFEVN' or 'Nepstech Wifi Router xpon'
    Affected if Device is Nepstech NTPL-Xpon1GFEVN model
  2. Check the firmware version
    Access router admin panel or use SNMP/CLI to retrieve firmware version; compare to 2.0.1
    Affected if Firmware version is 2.0.1 exactly (or if version cannot be determined but device is confirmed as the affected model)
  3. Verify Telnet service status
    Run 'telnet <router-ip> 2345' or use port scanner (nmap -p 2345 <router-ip>) to check if port 2345 is open and responding
    Affected if Telnet service is running and port 2345 is open and accessible
  4. Assess network exposure of Telnet port
    Check firewall rules or perform external port scan from untrusted network to confirm port 2345 is reachable from outside localhost
    Affected if Port 2345 is exposed to untrusted networks or the internet without firewall filtering

A user is affected if they own a Nepstech NTPL-Xpon1GFEVN router with firmware 2.0.1 and have Telnet on port 2345 accessible (even locally, as this indicates the vulnerable service is enabled).

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

Immediately restrict network access to port 2345 via firewall rules or disable the Telnet service if unused. Contact vendor for firmware update; if unavailable, consider network segmentation or device replacement.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-37855 — 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-37855 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