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. After heap shaping, an attacker can achieve code execution in the context of the cloud-brd binary that runs at the root level. This is fixed in ER605(UN)_v2_2.2.4 Build 020240119.
References
| Link | Resource |
|---|---|
| https://github.com/microsoft/Microsoft-TP-Link-Research-Team | Third Party Advisory |
| https://www.tp-link.com/us/omada-sdn/ | Product |
| https://github.com/microsoft/Microsoft-TP-Link-Research-Team | Third Party Advisory |
| https://www.tp-link.com/us/omada-sdn/ | Product |
Configurations
Configuration 1 (hide)
| AND |
|
History
No history.
Information
Published : 2024-03-14 16:15
Updated : 2025-09-18 16:30
NVD link : CVE-2024-25139
Mitre link : CVE-2024-25139
CVE.ORG link : CVE-2024-25139
JSON object : View
Products Affected
tp-link
- omada_er605
- omada_er605_firmware
CWE
CWE-120
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
