dbcve.org
Tl Sg105pe FirmwareOperating system · Tp Link

CVE-2023-22303

CRITICAL · 9.8 CVSS v3.1 Published 2023-01-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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 SG105PE firmware prior to 'TL-SG105PE(UN) 1.0_1.0.0 Build 20221208' contains an authentication bypass vulnerability. Under the certain conditions, an attacker may impersonate an administrator of the product. As a result, information may be obtained and/or the product's settings may be altered with the privilege of the administrator.

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 · moderate confidence

TP-Link SG105PE switch firmware prior to version TL-SG105PE(UN) 1.0_1.0.0 Build 20221208 contains an authentication bypass vulnerability that allows attackers to impersonate administrators under certain conditions, enabling unauthorized access to sensitive information and modification of device settings.

MitigationUpdate TP-Link SG105PE firmware to version TL-SG105PE(UN) 1.0_1.0.0 Build 20221208 or later to remediate the authentication bypass vulnerability.

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 Sg105pe FirmwareOperating system
Affected:= 1.0.0

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 checks

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

  1. Check the installed firmware version
    Access the TP-Link SG105PE web management interface and navigate to System > Firmware Upgrade, or use SNMP to query the device firmware version
    Affected if The firmware version is 1.0.0 or any version prior to TL-SG105PE(UN) 1.0_1.0.0 Build 20221208
  2. Verify the exact firmware build date
    In the web interface, locate the firmware version string which includes the build date; confirm whether the build date is earlier than 20221208
    Affected if The build date in the firmware version string is earlier than December 8, 2022
  3. Confirm remote management is enabled
    In the web interface, go to System > Management > Access Control and check if HTTP, HTTPS, or SNMP management access is enabled for LAN or WAN
    Affected if Remote management interfaces are enabled and the device is running a vulnerable firmware version

You are affected if your TP-Link SG105PE is running firmware version 1.0.0 or any version before TL-SG105PE(UN) 1.0_1.0.0 Build 20221208, and remote management is accessible.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update TP-Link SG105PE firmware to version TL-SG105PE(UN) 1.0_1.0.0 Build 20221208 or later to remediate the authentication bypass vulnerability.

Recommended fix High confidence

TL-SG105PE(UN) 1.0_1.0.0 Build 20221208

  1. Download the fixed firmware 'TL-SG105PE(UN) 1.0_1.0.0 Build 20221208' from the official TP-Link support website (www.tp-link.com)
  2. Access the TP-Link SG105PE web management interface by entering the device's IP address in a web browser
  3. Log in to the admin panel with administrator credentials
  4. Navigate to the 'System' or 'Maintenance' section, then find 'Firmware Upgrade' or 'Firmware Update'
  5. Click 'Browse' or 'Choose File' and select the downloaded firmware file
  6. Click 'Upgrade' or 'Upload' to begin the firmware update process
  7. Wait for the upgrade to complete - do not power off the device during this process
  8. The device will reboot automatically; verify the firmware version after reboot matches 'TL-SG105PE(UN) 1.0_1.0.0 Build 20221208'

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tl Sg105pe 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 help mitigating

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-2023-22303 — 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-2023-22303 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