Tl Ps310u FirmwareOperating system · Tp Link

CVE-2020-15055

HIGH · 8.8 CVSS v3.1 Published 2020-08-07
Fix available
A fix is available. Upgrade to 2.079.000.t0210 or later.
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
TP-Link USB Network Server TL-PS310U devices before 2.079.000.t0210 allow an attacker on the same network to bypass authentication via a web-administration request that lacks a password parameter.

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 TP-Link TL-PS310U USB Network Server has an authentication bypass vulnerability in its web administration interface. Attackers on the same local network can bypass authentication by submitting a web request that omits the password parameter entirely, allowing unauthorized access to the device's admin functions.

MitigationUpgrade the device firmware to version 2.079.000.t0210 or later to resolve the authentication bypass. If firmware updates are unavailable, restrict access to the web administration interface using network segmentation, firewall rules, or disabling remote administration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tl Ps310u FirmwareOperating system
Affected:< 2.079.000.t0210

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. Confirm device model
    Identify the device on your network by checking its IP address, MAC OUI (TP-Link vendor prefix), or by accessing the web interface and checking the device model displayed in the admin page header or status section
    Affected if Device is not a TP-Link TL-PS310U unit - this vulnerability only affects this specific model
  2. Check firmware version
    Access the web administration interface and navigate to the System or Firmware Upgrade section to view the current firmware version. Alternatively, check the device status page or any diagnostic output that displays the installed firmware build number
    Affected if Firmware version is lower than 2.079.000.t0210 (any build below this version number)
  3. Verify web administration interface accessibility
    Attempt to access the device web admin interface over HTTP/HTTPS from your local network. Confirm the login page loads and accepts authentication attempts
    Affected if Web administration interface is accessible from network segments accessible to untrusted users - the vulnerability allows bypass when the interface is exposed
  4. Confirm vulnerable authentication mechanism
    Review the login form on the web administration interface. Note whether the form includes a password parameter in the HTML source or network request when submitting credentials
    Affected if The login form submits a password parameter - the vulnerability exploits requests where this parameter is omitted entirely

You are affected if you have a TP-Link TL-PS310U device running firmware version below 2.079.000.t0210 with its web administration interface accessible from your network

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
Upgrade available Upgrade to 2.079.000.t0210 or later
Fixed in 2.079.000.t0210
Interim mitigation

Upgrade the device firmware to version 2.079.000.t0210 or later to resolve the authentication bypass. If firmware updates are unavailable, restrict access to the web administration interface using network segmentation, firewall rules, or disabling remote administration.

Fix this in Tl Ps310u Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-15055 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-15055 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