Talos Vulnerability Report

SUMMARY

A buffer overflow vulnerability exists in the adm.cgi set_wzdgw4G() functionality of Wavlink AC3000 M33A8.V5030.210505. A specially crafted HTTP request can lead to stack-based buffer overflow. An attacker can make an authenticated HTTP request to trigger this vulnerability.

CONFIRMED VULNERABLE VERSIONS

The versions below were either tested or verified to be vulnerable by Talos or confirmed to be vulnerable by the vendor.

Wavlink AC3000 M33A8.V5030.210505

PRODUCT URLS

Wavlink AC3000 - https://www.wavlink.com/en_us/product/WL-WN533A8.html

CVSSv3 SCORE

9.1 - CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

CWE

CWE-120 - Buffer Copy without Checking Size of Input (‘Classic Buffer Overflow’)

DETAILS

The Wavlink AC3000 wireless router is predominately one of the most popular gigabit routers in the US, in part due to both its potential wireless and wired speed capabilities and extremely low price point (costing at the time of this writing ~$60 USD). Among the configuration options, it’s also able to act as a standalone wireless gateway, a basic network router, or a wireless repeater.

When interacting with and configuring the Wavlink AC3000 wifi router, as is typical of most wifi routers, an administrator logs in via some web portal and configures appropriate options via the HTTP interface. In the case of this particular router, and in another somewhat common execution pattern, these HTML pages can invoke .cgi binaries due to how the lighttpd server is configured. Since all of these .shtml and .cgi files are located in the web root, anyone with network access to the device doesn’t actually need to log in to the device to interact with these .cgi files, and it usually is the responsibility of the .cgi binary to check if the authentication is completed successfully. On this device, one will see a check_valid_user() function in each individual .cgi binary which will check the session cookie of the HTTP request to see if it’s coming from a validly logged in user.

Assuming that we’ve passed this check in the adm.cgi binary, we then run into a set of functions that we can call based off of what we pass for the page= parameter in our HTTP POST request. Of the available commands, we focus on the following:

00401910                          else if (strcmp(webget_page, "wzdgw4G") == 0)
00401c4c                              set_wzdgw4G(contlen_buf)

If we provide page=wzdgw4G, we enter the set_wzdgw4G function and our provided POST data is further parsed therein:

00409208  int32_t set_wzdgw4G(int32_t arg1)
00409250      nvram_bufget(0, "OperationMode")
0040926c      nvram_bufget(0, "lan_ipaddr")
00409288      int32_t TouchLinkEn = nvram_bufget(0, "TouchLinkEn")
// [...]
004094b4      int32_t wlan_ssid2 = strdup(web_get("wlan_ssid2", arg1, 0)) // [1]
// [...]
00409978      if (strcmp(TouchLinkEn, "1") == 0)
00409d9c          void var_a0
00409d9c          sprintf(&var_a0, "%s_Touch", wlan_ssid2) // [2]
00409db8          nvram_bufset(2, "SSID3", &var_a0)

At [1], the binary copies our wlan_ssid2 POST parameter to the heap and then copies our input buffer to the stack at [2]. Since there’s no length checking on our input buffer, we can easily provide a buffer longer than 0xa0 bytes, which will overwrite the return address of this function and quickly result in arbitrary code execution.

Crash Information

Thread 2.1 "adm.cgi" hit Breakpoint 3, 0x00409d9c in set_wzdgw4G ()
(gdb) x/1s $a2
0x7fb108:       "\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177\bp\377\177", 'A' <repeats 16 times>
(gdb) c
Continuing.
[Detaching after fork from child process 19817]
[Detaching after fork from child process 19846]

Thread 2.1 "adm.cgi" received signal SIGSEGV, Segmentation fault.
0x41414141 in ?? ()
(gdb) info reg
          zero       at       v0       v1       a0       a1       a2       a3
 R0   00000000 00000000 00000000 ffffffff 00000003 7fc82dac 00000000 00000000
            t0       t1       t2       t3       t4       t5       t6       t7
 R8   00000000 00000000 00000000 00000000 00000001 00000000 00000000 00000001
            s0       s1       s2       s3       s4       s5       s6       s7
 R16  7fff7008 7fff7008 7fff7008 7fff7008 7fff7008 7fff7008 41414141 41414141
            t8       t9       k0       k1       gp       sp       s8       ra
 R24  00000000 77763450 00000010 00000000 77800490 7fc82f28 41414141 41414141
        status       lo       hi badvaddr    cause       pc
      0100fc13 00000400 00000000 41414140 50800008 41414141
          fcsr      fir      hi1      lo1      hi2      lo2      hi3      lo3
      00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
        dspctl  restart
      00000000 00000000

TIMELINE

2024-07-25 - Initial Vendor Contact
2024-07-29 - Requesting reply from vendor
2024-07-30 - Vendor confirms receipt
2024-07-30 - Vendor Disclosure
2024-07-30 - Vendor confirms receipt
2024-09-02 - Status update request sent
2024-10-15 - Status update request. Upcoming expiration date announced.
2024-10-22 - Vendor replies product has been discontinued, but patches are being worked on
2024-11-04 - Status update request for patch release dates
2024-11-12 TALOS advisory release date announced
2025-01-14 - Public Release