Omada 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. An attacker who obtains access to stored credential data may be able to recover valid credentials to gain unauthorized access to affected devices or management environments.

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 information being delivered to an attacker. Successful exploitation may allow disclosure of provisioning information intended for a legitimate device.

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 adoption-related communications may be able to recover session encryption keys and decrypt affected communications.

Omada devices rely on embedded certificates shared across deployments to establish trust between controllers and managed devices. An attacker who obtains these certificates can impersonate trusted controllers or devices and intercept communications.

The Omada adoption protocol uses hard-coded cryptographic keys to establish trust and protect authentication between controllers and managed devices. An attacker may impersonate a trusted controller or device and gain access to sensitive adoption-related communications.

The Omada device adoption process transmits authentication credentials using a weak hashing algorithm. An attacker intercepting the traffic may recover valid credentials and gain unauthorized access to managed devices.

In communication between Omada devices and cloud controllers, there is a certificate validation weakness. Certificate identity verification does not adequately check that the certificate matches the expected cloud controller hostname, potentially allowing certificate validation protections to be bypassed.