Critical · published March 11, 2025
🚨 Default service account credentials could let anyone waltz right into your PMM Server and take control! 🔥 Think of it like having a spare key to your house left under the mat, but instead of just being a way in, it’s a full-on blueprint for everything inside. An attacker can use this key to not only enter but also rearrange your entire living space! An attacker gaining SSH access could execute commands with root privileges, giving them unrestricted access to sensitive data and the ability to alter configurations. This situation could lead to data breaches, system downtime, and a significant loss of trust from your users — a catastrophic chain reaction!
Think of it like having a spare key to your house left under the mat, but instead of just being a way in, it’s a full-on blueprint for everything inside. An attacker can use this key to not only enter but also rearrange your entire living space! This vulnerability stems from the persistent use of default service account credentials in Percona PMM Server (OVA) prior to version 3.0.0-1.ova, allowing unauthorized access and elevated privileges through SSH and Sudo.
An attacker gaining SSH access could execute commands with root privileges, giving them unrestricted access to sensitive data and the ability to alter configurations. This situation could lead to data breaches, system downtime, and a significant loss of trust from your users — a catastrophic chain reaction! To safeguard your systems, immediately upgrade your PMM Server to versions 2.42.0-1.ova, 2.43.0-1.ova, 2.43.1-1.ova, 2.43.2-1.ova, 2.44.0-1.ova, or 3.0.0-1.ova and later. Additionally, ensure that all default credentials are changed to unique, secure values. Perform a security audit to identify and rectify any further vulnerabilities. You've got this! Follow these steps, and you’ll be back in control and fortified in no time! 🛡️