Critical · published December 10, 2025
🚨 A sneaky sscanf vulnerability in the check_cookie() function can let attackers write arbitrary data to fixed-size stack buffers! This means full device compromise is just a bad cookie away! 🔥 Think of it like a restaurant where an unscrupulous diner is allowed to write their own orders directly in the kitchen — if they sneak in a few extra items, they could completely change the meal being served! An attacker could completely hijack your device, gaining control over everything it manages. From stealing sensitive data to launching further attacks, the potential damage is absolutely devastating! You wouldn't want just anybody walking in and controlling your whole kitchen, right?
Think of it like a restaurant where an unscrupulous diner is allowed to write their own orders directly in the kitchen — if they sneak in a few extra items, they could completely change the meal being served! This vulnerability arises from unsafe calls to sscanf within the check_cookie() function, allowing unauthenticated attackers to exploit fixed-size stack buffers. By providing specially crafted input, they can overwrite critical memory areas, leading to arbitrary code execution.
An attacker could completely hijack your device, gaining control over everything it manages. From stealing sensitive data to launching further attacks, the potential damage is absolutely devastating! You wouldn't want just anybody walking in and controlling your whole kitchen, right? Immediate action is essential: ensure that all versions using this function are patched promptly. Update to the fixed version as soon as it is available, and implement rigorous input validation to protect against malformed data. Don't wait for an attack to happen! You’ve got this! Follow these steps, and you’ll be well on your way to securing your devices! 🛡️
| Product | Versions | Fixed in |
|---|---|---|
| wago/0852-1328_firmware | < 02.64 | 02.64 |
| wago/0852-1322_firmware | < 02.64 | 02.64 |