CVE-2022-29393

TOTOLINK N600R V4.3.0cu.7647_B20210106 was discovered to contain a stack overflow via the comment parameter in the function FUN_004192cc

published May 10, 2022

CVSS
—
EPSS
2%
Percentile
76.9
In the wild
Unconfirmed
What it is

⚠️ A sneaky stack overflow is lurking in the TOTOLINK N600R! This vulnerability can be triggered through the comment parameter, and it’s ready for mischief! Think of this like a crowded restaurant where a waiter accidentally spills endless orders into the kitchen — the kitchen can only handle so much before it overflows and chaos ensues! If exploited, this stack overflow can lead to unpredictable behavior in the router, potentially crashing the device or even allowing an attacker to execute arbitrary code. While it’s not currently reported as actively exploited, the risk is there, bubbling under the surface!

Put simply

Think of this like a crowded restaurant where a waiter accidentally spills endless orders into the kitchen — the kitchen can only handle so much before it overflows and chaos ensues! This vulnerability in version V4.3.0cu.7647_B20210106 of the TOTOLINK N600R allows a stack overflow through an improperly handled comment parameter in the function FUN_004192cc.

What to do

If exploited, this stack overflow can lead to unpredictable behavior in the router, potentially crashing the device or even allowing an attacker to execute arbitrary code. While it’s not currently reported as actively exploited, the risk is there, bubbling under the surface! To protect your devices, update to the latest firmware version from TOTOLINK as soon as possible. Regularly check for updates and consider implementing network segmentation to minimize exposure while you address this issue. You've got this! Stay vigilant and keep those routers updated for a secure network! 🛡️

The record
Technical detail
CVSS
Not scored
CVSS v4.0
Not supplied
EPSS
0.01692 · 76.9th percentile
Published
2022-05-10T19:49Z
EPSS history
Timeline
  • 10 MAY 19:49Z
    TOTOLINK N600R V4.3.0cu.7647_B20210106 was discovered to contain a stack overflow via the comment parameter in the function FUN_004192cc
    cvelistv5