GeoServer has a Server-Side Request Forgery (SSRF) Vulnerability in its XML Entity Resolution
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.26.4, 2.27.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
GeoServer is an open source server that allows users to share and edit geospatial data. Prior to versions 2.26.4 and 2.27.3, a GeoServer that uses `ENTITY_RESOLUTION_ALLOWLIST` may allow attacker to perform unauthenticated Server-Side Request Forgery (SSRF). This vulnerability requires that GeoServer is set up to use a proxy base URL and the `ENTITY_RESOLUTION_ALLOWLIST` (default since 2.25.0). Versions 2.26.4 and 2.27.3 contain a fix. GeoServer installations are only affected by this vulnerability if they use a proxy base URL that does not contain a URL path or end with a slash. If the proxy base URL does not contain a path, adding a slash to the end of the URL will mitigate this vulnerability.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- geoserver org.geoserver.web:gs-web-app
fixed in 2.26.4; From 2.27.0 · fixed in 2.27.3
- geoserver org.geoserver:gs-main
fixed in 2.26.4; From 2.27.0 · fixed in 2.27.3
- org.geoserver.web:gs-web-appMaven
fixed in 2.26.4
- org.geoserver:gs-mainMaven
fixed in 2.26.4
- org.geoserver:gs-mainMaven
From 2.27.0 · fixed in 2.27.3
- org.geoserver.web:gs-web-appMaven
From 2.27.0 · fixed in 2.27.3