dbcve.org
T2600g 28sq FirmwareOperating system · Tp Link

CVE-2023-28368

MEDIUM · 5.7 CVSS v3.1 Published 2023-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
No privileges

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 L2 switch T2600G-28SQ firmware versions prior to 'T2600G-28SQ(UN)_V1_1.0.6 Build 20230227' uses vulnerable SSH host keys. A fake device may be prepared to spoof the affected device with the vulnerable host key.If the administrator may be tricked to login to the fake device, the credential information for the affected device may be obtained.

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

The TP-Link T2600G-28SQ L2 switch uses vulnerable SSH host keys in firmware versions prior to T2600G-28SQ(UN)_V1_1.0.6 Build 20230227. An attacker can prepare a rogue device that spoofs the affected device using the same vulnerable host key, enabling a man-in-the-middle attack where administrator credentials can be captured if the admin logs into the fake device.

MitigationUpdate firmware to version T2600G-28SQ(UN)_V1_1.0.6 Build 20230227 or later, and regenerate SSH host keys on the device. Administrators should verify SSH host key fingerprints before initial connections to prevent credential theft.

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
T2600g 28sq FirmwareOperating system
Affected:= 20190530= 20200304

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:R/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 firmware version
    Access the switch web interface (or CLI via console/SSH) and navigate to System > Device Management or use the 'show version' command in CLI to retrieve the firmware build date and version number
    Affected if The firmware build date is 20190530, 20200304, or any version prior to T2600G-28SQ(UN)_V1_1.0.6 Build 20230227
  2. Confirm SSH management interface is enabled
    In the web UI, go to Management > Access Control > SSH or use 'show ip ssh' in CLI to verify if SSH access is enabled for administrative login
    Affected if SSH management access is enabled on the device (the vulnerability only applies when SSH is active)
  3. Check the SSH host key fingerprint
    On first SSH connection to the device, record the host key fingerprint displayed by your SSH client. Compare this against a known-good fingerprint obtained via console access or from trusted documentation
    Affected if The SSH host key fingerprint does not match the expected value or the key has not been regenerated since firmware installation (indicating static/vulnerable host keys may still be in use)

The device is affected if it runs firmware versions prior to T2600G-28SQ(UN)_V1_1.0.6 Build 20230227 AND has SSH management interface enabled, as these conditions indicate the device is using the vulnerable pre-generated SSH host keys.

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 firmware to version T2600G-28SQ(UN)_V1_1.0.6 Build 20230227 or later, and regenerate SSH host keys on the device. Administrators should verify SSH host key fingerprints before initial connections to prevent credential theft.

Recommended fix High confidence

T2600G-28SQ(UN)_V1_1.0.6 Build 20230227

  1. Obtain the firmware file 'T2600G-28SQ(UN)_V1_1.0.6 Build 20230227' from the official TP-Link support website (www.tp-link.com)
  2. Access the switch management web interface or console
  3. Navigate to the firmware upgrade section
  4. Upload the new firmware file
  5. Wait for the upgrade process to complete and the device to reboot
  6. Verify the firmware version has been updated to the fixed release

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

Fix this in T2600g 28sq Firmware 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-2023-28368 — 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-28368 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