Critical · published July 1, 2024
CVSS calls it critical at 9.8. It is confirmed in active exploitation. It sits in the 100.0th percentile for exploit probability.
🚨 Unauthenticated users can execute arbitrary code on GeoServer with just a crafted request! This is a major oversight that affects all default installations. 🔥 Think of GeoServer as a restaurant where anyone can walk in and cook in the kitchen without permission — they just need to know the right recipe to whip up chaos! This vulnerability means an attacker could stroll into your system and run whatever code they like, potentially leading to data breaches, unauthorized access, and system chaos. Imagine the devastation if someone could manipulate your geospatial data or take control of your server!
Think of GeoServer as a restaurant where anyone can walk in and cook in the kitchen without permission — they just need to know the right recipe to whip up chaos! The flaw exists because GeoServer improperly evaluates property names as XPath expressions, allowing malicious input to be executed as code. This vulnerability affects all instances due to a mix-up in how feature types are handled by the GeoTools library.
This vulnerability means an attacker could stroll into your system and run whatever code they like, potentially leading to data breaches, unauthorized access, and system chaos. Imagine the devastation if someone could manipulate your geospatial data or take control of your server! To protect your GeoServer, update to versions 2.22.6, 2.23.6, 2.24.4, or 2.25.2 immediately. If updating isn't an option right now, as a temporary workaround, remove the `gt-complex-x.y.jar` file to disable the vulnerable functionality, but be aware this might disrupt some features. You've got this! Secure your GeoServer and keep those geospatial data safe! 🛡️