Vulnerabilities

A cryptographic weakness exists in affected Omada devices where site credentials are protected using a legacy hashing algorithm that does not provide sufficient protection.

A race condition exists in the cloud-based Omada device adoption process when an attacker may be able to interact with the adoption workflow before a legitimate device completes registration, resulting in provisioning in…

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 sessio…

Affected Omada devices rely on embedded certificates that are shared across deployments to establish trust between controllers and managed devices.

A cryptographic weakness exists in the Omada adoption protocol.

A cryptographic weakness exists in the Omada device adoption process.

A certification validation weakness exists in communication between affected Omada devices and cloud controllers.

TP-Link Omada ER605 Reliance on Security Through Obscurity Vulnerability.

TP-Link Omada ER605 Buffer Overflow Remote Code Execution Vulnerability.

TP-Link Omada ER605 Stack-based Buffer Overflow Remote Code Execution Vulnerability.

TP-Link Omada ER605 Comexe DDNS Response Handling Heap-based Buffer Overflow Remote Code Execution Vulnerability.

TP-Link Omada ER605 PPTP VPN username Command Injection Remote Code Execution Vulnerability.

TP-Link Omada ER605 Access Control Command Injection Remote Code Execution Vulnerability.

TP-Link Omada ER605 DHCPv6 Client Options Stack-based Buffer Overflow Remote Code Execution Vulnerability.

In TP-Link Omada er605 1.0.1 through (v2.6) 2.2.3, a cloud-brd binary is susceptible to an integer overflow that leads to a heap-based buffer overflow.