← Back
CVE-2024-45747
Vulnerability in org.geoserver:gs-main (CVE-2024-45747)
Summary
vulnerability in org.geoserver:gs-main (CVE-2024-45747). Risk of unauthorized operations or information disclosure. Exploitable via ``GEOSERVER_FREEMARKER_BLOCK_LIST``. Mitigation: upgrade to `2.27.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-45747** has been found in org.geoserver:gs-main.
Attackers can target a specific entry point like ``GEOSERVER_FREEMARKER_BLOCK_LIST`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade org.geoserver:gs-main to **2.27.0** or later.
If unsure, ask your IT team or search "org.geoserver:gs-main CVE-2024-45747" on the vendor's site.
CVE-2024-45747 (org.geoserver:gs-main) — CWE-749 /
Attack surface: `GEOSERVER_FREEMARKER_BLOCK_LIST` / `GEOSERVER_FREEMARKER_ALLOW_LIST` / `GEOSERVER_FREEMARKER_API_EXPOSED`
Patched: `2.27.0` — apply immediately
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-749) exists in org.geoserver:gs-main. Attackers reach the vulnerable code path via ``GEOSERVER_FREEMARKER_BLOCK_LIST`` without authentication.
📍 Affected scope
org.geoserver:gs-main — . Attack surface: `GEOSERVER_FREEMARKER_BLOCK_LIST` / `GEOSERVER_FREEMARKER_ALLOW_LIST` / `GEOSERVER_FREEMARKER_API_EXPOSED`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.27.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'org.geoserver:gs-main' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'org.geoserver:gs-main' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.geoserver:gs-main` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade org.geoserver:gs-main to 2.27.0ステージング環境で 2.27.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.geoserver:gs-main
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.27.0"}]}]
maven
org.geoserver:gs-wms
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.27.0"}]}]
maven
org.geoserver.web:gs-web-app
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.27.0"}]}]
References
- web https://github.com/geoserver/geoserver/security/advisories/GHSA-wf6j-gr27-g7ch
- web https://github.com/geoserver/geoserver/pull/8164
- web https://docs.geoserver.org/latest/en/user/tutorials/GetFeatureInfo/html/#accessing-instance-methods
- web https://osgeo-org.atlassian.net/browse/GEOS-11645
- web https://osgeo-org.atlassian.net/browse/GEOS-11777
- web https://github.com/advisories/GHSA-wf6j-gr27-g7ch