Skip to content

Vendor

TP Link Systems Inc. vulnerabilities

28 published CVES affecting TP Link Systems Inc., from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
28
Critical
0
High
18
Medium
10
Low
0
Unscored
0
CISA KEV
0
Atom feed of TP Link Systems Inc. alerts

Products

Latest TP Link Systems Inc. CVEs

Newest publication first · page 1 of 2

  1. MediumCVSS 5.7 EPSS 0.30%

    A cryptographic weakness exists in affected Omada devices where site credentials are protected using a legacy hashing algorithm that does not provide sufficient protection. An attacker who obtains access to stored credential data may be able to recover valid credentials to gain u...

  2. MediumCVSS 6.9 EPSS 0.33%

    A cryptographic weakness exists in the Omada adoption protocol where session encryption keys used to protect communications between controllers and managed devices may be predictable due to insufficient entropy in session key generation. An attacker who successfully intercepts ad...

  3. HighCVSS 8.2 EPSS 0.32%

    Affected Omada devices rely on embedded certificates that are shared across deployments to establish trust between controllers and managed devices. An attacker who obtains the embedded certificates may be able to impersonate trusted controllers or devices and intercept affected c...

  4. MediumCVSS 6.9 EPSS 0.34%

    A cryptographic weakness exists in the Omada device adoption process. During adoption, authentication credentials associated with site management are transmitted using a weak hashing algorithm that does not provide sufficient protection. An attacker who successfully intercepts ad...

  5. HighCVSS 8.5 EPSS 2.5%

    A command injection vulnerability may be exploited after the admin's authentication in the VPN server configuration module on TP-Link Archer BE230 v1.2 and Archer AX73 v2. Successful exploitation could allow an attacker to gain full administrative control of the device, resulting...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.