published March 18, 2020
⚠️ An unauthenticated attacker can seize control by simply accessing port 9202 in the dep-holmes-engine-mgmt pod! Think of it as a restaurant kitchen that doesn’t lock the door to the back room. If someone can wander in and access the kitchen, they could potentially mess with the food prep and even change the menu! This vulnerability allows attackers with pod-to-pod communication to execute arbitrary code inside the pod. The implications could be quite serious, potentially leading to unauthorized access to sensitive systems and disruption of services.
Think of it as a restaurant kitchen that doesn’t lock the door to the back room. If someone can wander in and access the kitchen, they could potentially mess with the food prep and even change the menu! In ONAP HOLMES prior to the Dublin version, an issue exists that permits an attacker with pod communication access to exploit port 9202, resulting in arbitrary code execution within the pod.
This vulnerability allows attackers with pod-to-pod communication to execute arbitrary code inside the pod. The implications could be quite serious, potentially leading to unauthorized access to sensitive systems and disruption of services. To mitigate this risk, ensure timely upgrades to the latest version of ONAP HOLMES. Additionally, restrict access to port 9202, implementing proper network policies to safeguard pod communication. This is fixable! Stay proactive, secure your pods, and you'll keep your systems safe! 🛡️