Critical · published July 15, 2024
🚨 An authenticated RCE just lurks behind a URL! Thruk allows networked users to inject rogue commands during PDF report generation, handing them the keys to your monitoring kingdom. 🔥 Think of it like a hotel manager who can sneak extra instructions into a reservation request — if they write it just right, they could change the guest plans entirely, like switching their deluxe suite for a broom closet! An attacker with legitimate access can execute arbitrary commands on your server, opening the door to a complete takeover of the monitoring system. This could lead to devastating consequences, like data theft or unauthorized changes to configurations, leaving your entire system vulnerable. Yikes!
Think of it like a hotel manager who can sneak extra instructions into a reservation request — if they write it just right, they could change the guest plans entirely, like switching their deluxe suite for a broom closet! This vulnerability arises because Thruk fails to properly sanitize the URL parameter during PDF report generation. As a result, authorized users can manipulate command execution by injecting malicious code into the process that calls /script/html2pdf.sh.
An attacker with legitimate access can execute arbitrary commands on your server, opening the door to a complete takeover of the monitoring system. This could lead to devastating consequences, like data theft or unauthorized changes to configurations, leaving your entire system vulnerable. Yikes! Upgrade Thruk to version 3.16 immediately to mitigate the risk of this vulnerability. Since there are no known workarounds, ensuring your system runs the latest patched version is crucial for security. Don't delay! You've got this! Follow these steps, and your Thruk setup will be secure in no time. 🛡️