dbcve.org
GeoserverApplication · Osgeo

CVE-2023-41339

MEDIUM · 5.3 CVSS v3.1 Published 2023-10-25
Fix available
A fix is available. Upgrade to 2.22.5 / 2.23.2 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
GeoServer is an open source software server written in Java that allows users to share and edit geospatial data. The WMS specification defines an ``sld=<url>`` parameter for GetMap, GetLegendGraphic and GetFeatureInfo operations for user supplied "dynamic styling". Enabling the use of dynamic styles, without also configuring URL checks, provides the opportunity for Service Side Request Forgery. This vulnerability can be used to steal user NetNTLMv2 hashes which could be relayed or cracked externally to gain further access. This vulnerability has been patched in versions 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 · high confidence

GeoServer's WMS service contains an SSRF vulnerability via the unsanitized 'sld=' parameter in GetMap, GetLegendGraphic, and GetFeatureInfo operations. When dynamic styling is enabled without URL validation, attackers can supply arbitrary URLs causing the server to make requests on their behalf, enabling NetNTLMv2 hash theft for relay or cracking attacks.

MitigationUpgrade GeoServer to version 2.22.5 or 2.23.2. Additionally, configure URL checks for the sld parameter to prevent arbitrary URL loading.

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
GeoserverApplication
Affected:< 2.22.5>= 2.23.0, < 2.23.2

CVSS 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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify GeoServer version
    Check the installed GeoServer version via the web UI (About > Version) or by inspecting the geoserver.war/version.properties or pom.xml in the installation directory
    Affected if version is less than 2.22.5, or version is 2.23.0 or 2.23.1
  2. Confirm WMS service is enabled
    Check the WMS service configuration in GeoServer web UI under Services > WMS, or inspect the wms.xml configuration file in the data directory
    Affected if WMS service is enabled and the version check shows a vulnerable version
  3. Verify if dynamic styling is enabled
    Check WMS service settings for dynamic styling (SLD) configuration. This may appear as 'Dynamic Styling', 'Allow SLD', or 'SLD parsing' settings in the WMS service configuration panel
    Affected if Dynamic styling/SLD support is enabled on the WMS service AND the version is vulnerable
  4. Check sld parameter URL validation
    Inspect the security or validation settings for the sld parameter in the WMS service configuration. Look for URL allowlist, URL validation, or external entity settings related to SLD processing
    Affected if URL validation or allowlist for the sld parameter is not configured or is disabled

A user is affected if they run a vulnerable GeoServer version (below 2.22.5 or between 2.23.0-2.23.1) with WMS enabled and dynamic styling configured without URL validation on the sld parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.22.5 / 2.23.2 or later
Fixed in 2.22.52.23.2
Interim mitigation

Upgrade GeoServer to version 2.22.5 or 2.23.2. Additionally, configure URL checks for the sld parameter to prevent arbitrary URL loading.

Recommended fix High confidence

Upgrade to GeoServer 2.22.5 or 2.23.2 (depending on your current version branch)

  1. Backup your current GeoServer installation, data directory, and configuration
  2. Determine your current GeoServer version series (2.22.x or 2.23.x) to select the appropriate upgrade target
  3. Download the fixed version: 2.22.5 if currently on 2.22.x branch, or 2.23.2 if currently on 2.23.x branch
  4. Stop the GeoServer service
  5. Replace the GeoServer application files with the new version (or redeploy using your container/JVM method)
  6. Start the GeoServer service
  7. Verify the upgrade was successful by checking the GeoServer version in the About/Status page
  8. Test that WMS GetMap, GetLegendGraphic, and GetFeatureInfo operations still function correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Geoserver Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-41339 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-41339 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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