### Summary A vulnerability exists that allows an authenticated administrator with access to GeoServer's security system to pass arbitrary file names to the Master Password Dump web page and create files containing the master password in plaintext. The provided file name must be an absolute path to the target file, the target file can not already exist and all parent directories must already exist. ### Details When dumping the master password, GeoServer will use the provided file name with minimal validation as long as it is a java.io.File path. The only limitation is that the fix for a previous, unrelated vulnerability prevents relative path traversal here but absolute paths can be used to access arbitrary files. GeoServer does not enforce a maximum password length by default which allows an administrator to place malicious code into their password which could then be dumped into a JSP file. ### Impact #### Remote Code Execution (High severity) This vulnerability can lead to executing arbitrary code if GeoServer is deployed in an environment where an attacker can dynamically deploy and execute a JSP file. This is possible if the geoserver.war file is simply placed into the webapps directory of a default Tomcat installation. #### NTLM Hash Disclosure (Moderate severity) If GeoServer is deployed in a Windows operating system and the GeoServer administrator does not already have access to the Windows account running the GeoServer process, it may be possible for the administrator to make GeoServer trigger an outbound NTLM request to a remote, attacker-controlled server and gain access to the NTLM hash or user password for use in future attacks. #### Denial of Service (Low severity) This vulnerability allows writing a file to any location where the GeoServer process has write permissions which could still potentially cause some kind of denial of service. ### Mitigation GeoServer installations where the web interface is either disabled or completely removed are not affected since the vulnerability exists in one of the web pages. ### Resources https://osgeo-org.atlassian.net/browse/GEOS-11852 https://github.com/geoserver/geoserver/pull/8584
### Summary A vulnerability exists that allows an authenticated administrator with access to GeoServer's security system to pass arbitrary file names to the Master Password Dump web page and create files containing the master password in plaintext. The provided file name must be an absolute path to the target file, the target file can not already exist and all parent directories must already exist. ### Details When dumping the master password, GeoServer will use the provided file name with minimal validation as long as it is a java.io.File path. The only limitation is that the fix for a previous, unrelated vulnerability prevents relative path traversal here but absolute paths can be used to access arbitrary files. GeoServer does not enforce a maximum password length by default which allows an administrator to place malicious code into their password which could then be dumped into a JSP file. ### Impact #### Remote Code Execution (High severity) This vulnerability can lead to executing arbitrary code if GeoServer is deployed in an environment where an attacker can dynamically deploy and execute a JSP file. This is possible if the geoserver.war file is simply placed into the webapps directory of a default Tomcat installation. #### NTLM Hash Disclosure (Moderate severity) If GeoServer is deployed in a Windows operating system and the GeoServer administrator does not already have access to the Windows account running the GeoServer process, it may be possible for the administrator to make GeoServer trigger an outbound NTLM request to a remote, attacker-controlled server and gain access to the NTLM hash or user password for use in future attacks. #### Denial of Service (Low severity) This vulnerability allows writing a file to any location where the GeoServer process has write permissions which could still potentially cause some kind of denial of service. ### Mitigation GeoServer installations where the web interface is either disabled or completely removed are not affected since the vulnerability exists in one of the web pages. ### Resources https://osgeo-org.atlassian.net/browse/GEOS-11852 https://github.com/geoserver/geoserver/pull/8584
Update org.geoserver.web:gs-web-app to 2.27.3; org.geoserver.web:gs-web-app to 2.26.4; org.geoserver.web:gs-web-sec-core to 2.27.3; org.geoserver.web:gs-web-sec-core to 2.26.4 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanGeoServer has an arbitrary file write vulnerability in its Master Password Dump Page affects org.geoserver.web:gs-web-app (maven), org.geoserver.web:gs-web-app (maven), org.geoserver.web:gs-web-sec-core (maven), org.geoserver.web:gs-web-sec-core (maven). Severity is high. ### Summary A vulnerability exists that allows an authenticated administrator with access to GeoServer's security system to pass arbitrary file names to the Master Password Dump web page and create files containing the master password in plaintext. The provided file name must be an absolute path to the target file, the target file can not already exist and all parent directories must already exist. ### Details When dumping the master password, GeoServer will use the provided file name with minimal validation as long as it is a java.io.File path. The only limitation is that the fix for a previous, unrelated vulnerability prevents relative path traversal here but absolute paths can be used to access arbitrary files. GeoServer does not enforce a maximum password length by default which allows an administrator to place malicious code into their password which could then be dumped into a JSP file. ### Impact #### Remote Code Execution (High severity) This vulnerability can lead to executing arbitrary code if GeoServer is deployed in an environment where an attacker can dynamically deploy and execute a JSP file. This is possible if the geoserver.war file is simply placed into the webapps directory of a default Tomcat installation. #### NTLM Hash Disclosure (Moderate severity) If GeoServer is deployed in a Windows operating system and the GeoServer administrator does not already have access to the Windows account running the GeoServer process, it may be possible for the administrator to make GeoServer trigger an outbound NTLM request to a remote, attacker-controlled server and gain access to the NTLM hash or user password for use in future attacks. #### Denial of Service (Low severity) This vulnerability allows writing a file to any location where the GeoServer process has write permissions which could still potentially cause some kind of denial of service. ### Mitigation GeoServer installations where the web interface is either disabled or completely removed are not affected since the vulnerability exists in one of the web pages. ### Resources https://osgeo-org.atlassian.net/browse/GEOS-11852 https://github.com/geoserver/geoserver/pull/8584
AI coding agents often install or upgrade packages automatically in maven. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| org.geoserver.web:gs-web-appmaven | >=2.27.0,<=2.27.2 | 2.27.3 |
| org.geoserver.web:gs-web-appmaven | <=2.26.3 | 2.26.4 |
| org.geoserver.web:gs-web-sec-coremaven | >=2.27.0,<=2.27.2 | 2.27.3 |
| org.geoserver.web:gs-web-sec-coremaven | <=2.26.3 | 2.26.4 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate org.geoserver.web:gs-web-app to 2.27.3; org.geoserver.web:gs-web-app to 2.26.4; org.geoserver.web:gs-web-sec-core to 2.27.3; org.geoserver.web:gs-web-sec-core to 2.26.4 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanGeoServer has an arbitrary file write vulnerability in its Master Password Dump Page affects org.geoserver.web:gs-web-app (maven), org.geoserver.web:gs-web-app (maven), org.geoserver.web:gs-web-sec-core (maven), org.geoserver.web:gs-web-sec-core (maven). Severity is high. ### Summary A vulnerability exists that allows an authenticated administrator with access to GeoServer's security system to pass arbitrary file names to the Master Password Dump web page and create files containing the master password in plaintext. The provided file name must be an absolute path to the target file, the target file can not already exist and all parent directories must already exist. ### Details When dumping the master password, GeoServer will use the provided file name with minimal validation as long as it is a java.io.File path. The only limitation is that the fix for a previous, unrelated vulnerability prevents relative path traversal here but absolute paths can be used to access arbitrary files. GeoServer does not enforce a maximum password length by default which allows an administrator to place malicious code into their password which could then be dumped into a JSP file. ### Impact #### Remote Code Execution (High severity) This vulnerability can lead to executing arbitrary code if GeoServer is deployed in an environment where an attacker can dynamically deploy and execute a JSP file. This is possible if the geoserver.war file is simply placed into the webapps directory of a default Tomcat installation. #### NTLM Hash Disclosure (Moderate severity) If GeoServer is deployed in a Windows operating system and the GeoServer administrator does not already have access to the Windows account running the GeoServer process, it may be possible for the administrator to make GeoServer trigger an outbound NTLM request to a remote, attacker-controlled server and gain access to the NTLM hash or user password for use in future attacks. #### Denial of Service (Low severity) This vulnerability allows writing a file to any location where the GeoServer process has write permissions which could still potentially cause some kind of denial of service. ### Mitigation GeoServer installations where the web interface is either disabled or completely removed are not affected since the vulnerability exists in one of the web pages. ### Resources https://osgeo-org.atlassian.net/browse/GEOS-11852 https://github.com/geoserver/geoserver/pull/8584
AI coding agents often install or upgrade packages automatically in maven. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| org.geoserver.web:gs-web-appmaven | >=2.27.0,<=2.27.2 | 2.27.3 |
| org.geoserver.web:gs-web-appmaven | <=2.26.3 | 2.26.4 |
| org.geoserver.web:gs-web-sec-coremaven | >=2.27.0,<=2.27.2 | 2.27.3 |
| org.geoserver.web:gs-web-sec-coremaven | <=2.26.3 | 2.26.4 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard