ESP-IDF buffer overflow in lwIP DNS cached lookups
espressif esp-idf
espressif esp-idf
| Product | Affected | Fixed in |
|---|---|---|
| espressif esp-idf |
| No fix yet |
ESP-IDF is the Espressif Internet of Things (IOT) Development Framework. From 5.2.3 until 5.3.7, 5.4.5, 5.5.6, and 6.0.3, the lwIP DNS resolver's cached-lookup path in dns_lookup() in dns.c copies every cached address into a caller-provided single ip_addr_t output buffer without a length parameter or bounds check. When CONFIG_LWIP_DNS_MAX_HOST_IP is greater than 1 and a cached hostname has multiple A or AAAA records, a subsequent lookup through dns_gethostbyname() or dns_gethostbyname_addrtype() writes beyond the single-element buffer into adjacent stack memory. A network-positioned attacker who influences DNS responses can cause a reboot through stack-canary corruption or, without stack protection, overwrite stack variables with attacker-controlled address bytes and potentially redirect control flow. This issue is fixed in versions 5.5.6 and 6.0.3 and is scheduled to be fixed in versions 5.3.7 and 5.4.5. No fixed release is available for the end-of-life 5.2 line.
From the CVE record · GitHub_M
The lwIP DNS resolver in affected ESP-IDF versions can write multiple cached addresses beyond a single-address stack buffer when CONFIG_LWIP_DNS_MAX_HOST_IP is greater than 1. A network-positioned attacker who influences DNS responses can trigger a reboot or, without stack protection, potentially redirect control flow. No authentication or user interaction is described.
Engineers running ESP-IDF from 5.2.3 on the affected 5.2, 5.3, 5.4, 5.5, or 6.0 lines should check their versions and DNS configuration.