CVE Intelligence

Vulnerabilidades do TP-Link Systems Inc. Omada Sg2016p Firmware

🔔 Criar alerta RSS Verificador de versão

CVEs publicadas que afetam TP-Link Systems Inc. Omada Sg2016p Firmware: 8 registro(s), com versões afetadas e correções.
cpe:2.3:o:tp-link:omada_sg2016p_firmware

CVE-2025-15631 Média · 5.9 CWE-759 03/08/2026
Weak Credential Storage in TP-Link Omada Devices
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.
CVE-2025-15630 Média · 5.9 CWE-362 03/08/2026
Device Provisioning Race Condition in TP-Link Omada Adoption Workflow
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.
CVE-2025-15629 Alta · 7.5 CWE-331 03/08/2026
Weak Session Key Generation in TP-Link Omada Adoption Protocol
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.
CVE-2025-15628 Alta · 7.5 CWE-798 03/08/2026
Hardcoded Certificates in TP-Link Omada Device Communications
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 communications.
CVE-2025-15627 Alta · 7.5 CWE-321 03/08/2026
Hardcoded Cryptographic Keys in TP-Link Omada Adoption Protocol Authentication
A cryptographic weakness exists in the Omada adoption protocol.  The protocol relies on hard-coded cryptographic keys to establish trust and protect authentication exchanges between controllers and managed devices during device adoption. An attacker may be able to impersonate trusted controllers or managed devices and gain access to sensitive adoption-related communications.
CVE-2025-15544 Média · 5.9 CWE-759 03/08/2026
Weak Credential Protection During TP-Link Omada Device Adoption
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 adoption-related authentication traffic may be able to recover valid credentials and gain unauthorized access to managed devices or controller-managed environments.
CVE-2025-9291 Média · 6.5 CWE-295 03/08/2026
Improper Certificate Validation in TP-Link Omada Cloud Communications
A certification validation weakness exists in communication between affected Omada devices and cloud controllers. Certificate identity verification does not adequately validate that a presented certificate corresponds to the expected cloud controller hostname, which may allow certificate validation protections to be bypassed under specific conditions. Successful exploitation may allow interception or modification of communication between affected devices and cloud controllers.
CVE-2026-1668 Crítica · 9.8 CWE-787 13/03/2026
Input Validation Vulnerability on Multiple Omada Switches
The web interface on multiple Omada switches does not adequately validate certain external inputs, which may lead to out-of-bound memory access when processing crafted requests. Under specific conditions, this flaw may result in unintended command execution.<br>An unauthenticated attacker with network access to the affected interface may cause memory corruption, service instability, or information disclosure. Successful exploitation may allow remote code execution or denial-of-service.