Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2025-58175 medium CVSS 6.5

Vulnerability in org.geoserver.web:gs-web-app (CVE-2025-58175)

Summary

Vulnerability in org.geoserver.web:gs-web-app (CVE-2025-58175). Confidential information can be exposed externally. Exploitable via ENTITY_RESOLUTION_ALLOWLIST. Mitigation: upgrade to 2.27.3 or later.

Original description

The description as published by the source.

Summary

A GeoServer that uses ENTITY_RESOLUTION_ALLOWLIST may allow attacker to perform unauthenticated Server-Side Request Forgery (SSRF).

Details

This vulnerability requires that GeoServer is set up to use a proxy base URL and the ENTITY_RESOLUTION_ALLOWLIST (default since 2.25.0):

Impact

This vulnerability allows an attacker to cause GeoServer to make requests to an unintended location.

Workaround

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 (e.g., https://somesite.org instead of https://somesite.org/ or https://somesite.org/geoserver). If the proxy base URL does not contain a path, adding a slash to the end of the URL will mitigate this vulnerability.

Resources

https://osgeo-org.atlassian.net/browse/GEOS-11867
https://github.com/geoserver/geoserver/pull/8622

Credits:

  • Le Mau Anh Phong at Verichains Cyber Force

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-58175 has been found in org.geoserver.web:gs-web-app.
Attackers can target a specific entry point like ENTITY_RESOLUTION_ALLOWLIST over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade org.geoserver.web:gs-web-app to 2.27.3 or later.
If unsure, ask your IT team or search "org.geoserver.web:gs-web-app CVE-2025-58175" on the vendor's site.

CVE-2025-58175 (org.geoserver.web:gs-web-app) — CWE-20 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: ENTITY_RESOLUTION_ALLOWLIST
Patched: 2.27.3 — apply immediately
Workaround: 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 (e.g., https://somesite.org instead of https://somesite.org/ or https://somesite.org/geoserver).
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-20) exists in org.geoserver.web:gs-web-app. Attackers reach the vulnerable code path via ENTITY_RESOLUTION_ALLOWLIST without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of org.geoserver.web:gs-web-app. Attack surface: ENTITY_RESOLUTION_ALLOWLIST.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 2.27.3.

🛡️ Workaround

Workaround: 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 (e.g., https://somesite.org instead of https://somesite.org/ or https://somesite.org/geoserver).

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.geoserver.web:gs-web-app を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply temporary workaround mitigate 
    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 (e.g., `https://somesite.org` instead of `https://somesite.org/` or `https://somesite.org/geoserver`).

    パッチが適用されるまでの応急処置として、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 (e.g., https://somesite.org instead of https://somesite.org/ or https://somesite.org/geoserver). を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade org.geoserver.web:gs-web-app to 2.27.3

    ステージング環境で 2.27.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.geoserver.web:gs-web-app
[{"type":"ECOSYSTEM","events":[{"introduced":"2.27.0"},{"fixed":"2.27.3"}]}]
maven org.geoserver:gs-main
[{"type":"ECOSYSTEM","events":[{"introduced":"2.27.0"},{"fixed":"2.27.3"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details