CVE-2025-27505
BaseFortify
Publication date: 2025-06-10
Last updated on: 2025-08-26
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| osgeo | geoserver | to 2.25.6 (exc) |
| osgeo | geoserver | From 2.26.0 (inc) to 2.26.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-27505 is a vulnerability in GeoServer's REST API security where the default security controls protect the /rest path and its subpaths but fail to secure the /rest path when accessed with an extension (e.g., /rest.html). This allows unauthorized users to bypass the REST API security and access the REST API index page, which can disclose information about installed extensions. The issue arises because the security configuration does not properly handle REST API endpoints with extensions in their paths. [1, 2]
How can this vulnerability impact me? :
This vulnerability can allow unauthorized users to access the REST API index page of GeoServer without proper authorization. As a result, sensitive information about installed extensions may be disclosed, potentially aiding attackers in further exploiting the system. Although the impact is limited to information disclosure (low confidentiality impact), it can still pose a security risk by revealing system details to attackers. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by checking if your GeoServer instance allows access to the REST API index page via paths with extensions such as /rest.html without proper authorization. A simple way to test this is to send HTTP requests to the GeoServer REST API endpoints with extensions and observe if access is granted without authentication. For example, you can use curl commands like: 1) curl -i http://<geoserver-host>/rest.html 2) curl -i http://<geoserver-host>/gwc/rest.html If these requests return the REST API index page or other information without requiring authentication, your system is vulnerable. [2]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability immediately, modify the GeoServer security configuration file located at ${GEOSERVER_DATA_DIR}/security/config.xml. Change the REST filter paths to /rest.* and /rest/**, and similarly change the GWC filter paths to /gwc/rest.* and /gwc/rest/**. After making these changes, restart the GeoServer service to apply the new security settings. Additionally, upgrading GeoServer to version 2.26.3 or 2.25.6 or later will fully fix the vulnerability. [2, 1]