CVE-2024-25139: TP-Link Omada er605 · Classic Buffer Overflow
Source CVE Database V5
Not known to be exploited · CVSS 10.0 Critical.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Mar 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
To mitigate CVE-2024-25139, organizations should immediately upgrade all affected TP-Link Omada ER605 devices to firmware version 2.2.4 or later, where the vulnerability is patched. Network administrators should verify the firmware version on all devices and apply the update as a priority. Until the patch is applied, it is advisable to restrict network access to the management interfaces of the affected devices, ideally limiting access to trusted internal networks or VPNs. Employ network segmentation to isolate critical infrastructure from vulnerable devices. Monitor network traffic for unusual activity that could indicate exploitation attempts, such as unexpected connections to the cloud-brd process or anomalous command execution patterns. Implement intrusion detection and prevention systems (IDS/IPS) with signatures tuned for buffer overflow attempts targeting TP-Link devices. Regularly audit device configurations and logs for signs of compromise. Additionally, maintain an inventory of all network devices to ensure no affected units are overlooked during remediation efforts.
Description
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.