dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-46280

HIGH · 8.8 CVSS v3.1 Published 2024-09-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
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
PIX-LINK LV-WR22 RE3002-P1-01_V117.0 is vulnerable to Improper Access Control. The TELNET service is enabled with weak credentials for a root-level account, without the possibility of changing them.

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 PIX-LINK LV-WR22 RE3002-P1-01_V117.0 router has TELNET service enabled with hardcoded weak credentials that provide root-level access, and users cannot change these credentials due to firmware limitations, allowing remote attackers to gain full control of the device.

MitigationDisable the TELNET service through device configuration if possible, or implement network access controls to restrict TELNET access; if the service cannot be disabled or secured, replace the device with a supported model that allows credential management.

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
High
Availability
High

CVSS:3.1/AV:A/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 device model and firmware version
    Check the device label, web interface, or administrative panel for the exact model number PIX-LINK LV-WR22 RE3002-P1-01 and firmware version V117.0
    Affected if The device matches the affected model and firmware version
  2. Detect if TELNET service is listening
    Scan the device from the local network using a port scanner (such as nmap) targeting port 23 (TELNET)
    Affected if Port 23 is open and accepting TELNET connections
  3. Verify remote TELNET accessibility
    Attempt to connect to the device TELNET service from an external network or check if port 23 is exposed to the internet via router port forwarding or firewall rules
    Affected if TELNET service is reachable from outside the local network
  4. Confirm hardcoded credential access
    Attempt to authenticate to the TELNET service using known weak or default credentials for this device
    Affected if Authentication succeeds with root-level access using hardcoded credentials

The device is affected if it is a PIX-LINK LV-WR22 RE3002-P1-01 with firmware V117.0 that has TELNET port 23 exposed and accessible using hardcoded credentials.

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

Disable the TELNET service through device configuration if possible, or implement network access controls to restrict TELNET access; if the service cannot be disabled or secured, replace the device with a supported model that allows credential management.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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