Impact
The GeoTools library has a number of data sources that can perform unchecked JNDI lookups, which in turn can be used to perform class deserialization and result in arbitrary code execution.
Similar to the Log4J case, the vulnerability can be triggered if the JNDI name is user-provided.
As an example this can happen in GeoServer, but requires admin-level login to be triggered.
Patches
The lookups are now restricted in GeoTools 26.4, GeoTools 25.6, and GeoTools 24.6.
See User Guide update instructions, and GeoTools utility class instructions, when updating to a patched version.
Workarounds
The downstream application should not allow usage of remotely provided JNDI strings.
For example, in GeoServer, make the GUI (geoserver/web) and the REST configuration (geoserver/rest) unreachable from remote hosts.
aaime Analyst
mbadanoiu Analyst
jodygarnett Analyst
Impact
The GeoTools library has a number of data sources that can perform unchecked JNDI lookups, which in turn can be used to perform class deserialization and result in arbitrary code execution.
Similar to the Log4J case, the vulnerability can be triggered if the JNDI name is user-provided.
As an example this can happen in GeoServer, but requires admin-level login to be triggered.
Patches
The lookups are now restricted in GeoTools 26.4, GeoTools 25.6, and GeoTools 24.6.
See User Guide update instructions, and GeoTools utility class instructions, when updating to a patched version.
Workarounds
The downstream application should not allow usage of remotely provided JNDI strings.
For example, in GeoServer, make the GUI (
geoserver/web) and the REST configuration (geoserver/rest) unreachable from remote hosts.