GHSA-68cf-j696-wvv9 json
GeoServer vulnerable to SSRF in TestWfsPost for specific targets, e.g. PHP + Nginx
published last yr. modified last yr.
- cvss
- 7.5
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
### Summary
Missing checks allow for SSRF to specific targets using the TestWfsPost enpoint.
### Mitigation
To manage the proxy base value as a system administrator, use the parameter ``PROXY_BASE_URL`` to provide a non-empty value that cannot be overridden by the user interface or incoming request.[thomsmith](https://github.com/thomsmith).
### Resolution
The TestWfsPost has been replaced in GeoServer 2.25.2 and GeoServer 2.24.4 with a JavaScript [Demo Requests](https://docs.geoserver.org/latest/en/user/configuration/demos/index.html#demo-requests) page to test OGC Web Services.
### References
* [CVE-2024-29198](https://github.com/geoserver/geoserver/security/advisories/GHSA-5gw5-jccf-6hxw) Unauthenticated SSRF via TestWfsPost
Patch / fix
- maven org.geoserver:gs-wfs 2.24.4, 2.25.2
Is GHSA-68cf-j696-wvv9 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.geoserver:gs-wfs | >=1.0.0, <2.24.4 >=2.25.0, <2.25.2 |
2.24.4 2.25.2 |
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
Sources
- GitHub Advisory GHSA-68cf-j696-wvv9
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.