CVE-2023-43795
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGeoServer is an open source software server written in Java that allows users to share and edit geospatial data. The OGC Web Processing Service (WPS) specification is designed to process information from any server using GET and POST requests. This presents the opportunity for Server Side Request Forgery. This vulnerability has been patched in version 2.22.5 and 2.23.2.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceGeoServer versions prior to 2.22.5 and 2.23.2 contain a Server Side Request Forgery (SSRF) vulnerability in the OGC Web Processing Service (WPS) component. The WPS accepts GET and POST requests without proper validation, allowing attackers to coerce the server into making arbitrary outbound requests to internal or external resources.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.22.5>= 2.23.0, < 2.23.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine GeoServer versionLog into the GeoServer administration web interface and navigate to the 'About' > 'Version' page, or check the geoserver.war or geotools version metadata if you have file system access.Affected if The installed version is less than 2.22.5, or is 2.23.0 or 2.23.1.
-
Confirm WPS module is enabledIn the GeoServer admin interface, go to 'WPS' under the 'Services' section, or check the web.xml and associated WPS configuration files in the deployment for the wps service bean.Affected if The WPS service is listed as enabled or available in the services configuration.
-
Verify WPS endpoint is publicly accessibleCheck network access controls, firewall rules, and the GeoServer proxy configuration to determine if the /wps endpoint can be reached from untrusted networks.Affected if The WPS endpoint (typically at /geoserver/wps) is accessible from external or untrusted networks without network-level restrictions.
-
Identify if WPS lacks request validation controlsReview the WPS service configuration or proxy settings for any allowlist/denylist rules on the external requests the WPS can make, or test the WPS Execute endpoint with a known internal URL to observe if the server attempts to fetch it.Affected if There are no explicit allowlist restrictions on outbound URLs that the WPS can request, or the test request to an internal resource succeeds.
You are affected if your GeoServer version is less than 2.22.5 or between 2.23.0 and 2.23.1 AND the WPS endpoint is enabled and accessible, allowing arbitrary outbound requests without validation controls.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.22.52.23.2
Upgrade GeoServer to version 2.22.5 or 2.23.2 or later to apply the patched code. If immediate patching is not possible, restrict WPS endpoint access via network segmentation or firewall rules.
Upgrade to GeoServer 2.22.5 or 2.23.2 (both contain the SSRF vulnerability fix)
- Identify the currently running GeoServer version
- Back up the GeoServer data directory, configuration files, and any custom extensions
- Download GeoServer 2.22.5 (for users on 2.22.x line) or 2.23.2 (for users on 2.23.x line) from the official GeoServer download page
- Stop the GeoServer application service
- Replace the GeoServer installation with the new version, preserving the data directory
- Start GeoServer and verify the application runs successfully
- Verify the WPS endpoint is functional and the SSRF vulnerability is patched by testing that arbitrary external URLs can no longer be requested through WPS requests
- Review GeoServer logs for any errors post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43795 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-43795 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data