CVE-2024-25139
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.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.88%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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.
- CVSS 3.1
- 10.0 CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- EPSS
- 0.88% probability · 57th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-120
- Affected
- tp-link/omada er605 firmware
- Source
- cve@mitre.org
References
- https://github.com/microsoft/Microsoft-TP-Link-Research-TeamThird Party Advisory
- https://www.tp-link.com/us/omada-sdn/Product
- https://github.com/microsoft/Microsoft-TP-Link-Research-TeamThird Party Advisory
- https://www.tp-link.com/us/omada-sdn/Product
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.