GHSA-5PR3-M5HM-9956

Vulnerability from github – Published: 2023-10-24 19:21 – Updated: 2023-10-27 21:04
VLAI?
Summary
WPS Server Side Request Forgery vulnerability
Details

Summary

The OGC Web Processing Service (WPS) specification is designed to process information from any server using GET and POST requests.

This presents the opportunity for Server Side Request Forgery.

Details

This vulnerability requires:

  • The WPS extension to be installed
  • The WPS security setting "Disable complex inputs" to be unselected
  • Security URL checks to be disabled

Impact

This vulnerability presents the opportunity for Server Side Request Forgery.

Mitigation

The ability to reference an external URL location is defined by the WPS standard Execute operation. This operations is defined by an Industry and International standard and cannot be redefined by the GeoServer application in isolation.

To disable complex remote inputs on GeoServer 2.20.5 and GeoServer 2.21.0:

  1. Navigate to Security > WPS Security page
  2. Locate Complex Inputs heading
  3. Select the check box for Disable loading complex inputs from remote references

Resolution

To allow processing of complex inputs safely in GeoServer 2.22.5 and GeoServer 2.23.2:

  1. Navigate to Security > URL Checks
  2. Enable URL Checks are enabled setting
  3. Check the user manual for examples of how to trust specific locations for your external services.

Processing of complex inputs safely is on by default in GeoServer 2.24.0.

References

Severity ?
8.6 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.geoserver.extension:gs-wps-core"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.22.5"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.geoserver.extension:gs-wps-core"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.23.0"
            },
            {
              "fixed": "2.23.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2023-43795"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2023-10-24T19:21:02Z",
    "nvd_published_at": "2023-10-25T18:17:32Z",
    "severity": "HIGH"
  },
  "details": "### Summary\n\nThe OGC Web Processing Service (WPS) specification is designed to process information from any server using GET and POST requests.\n\nThis presents the opportunity for Server Side Request Forgery.\n\n## Details\n\nThis vulnerability requires:\n\n* The WPS extension to be installed\n* The WPS security setting \"Disable complex inputs\" to be unselected\n* Security URL checks to be disabled\n\n### Impact\n\nThis vulnerability presents the opportunity for Server Side Request Forgery.\n\n### Mitigation\n\nThe ability to reference an external URL location is defined by the WPS standard Execute operation. This operations is defined by an Industry and International standard and cannot be redefined by the GeoServer application in isolation.\n\nTo disable complex remote inputs on GeoServer 2.20.5 and GeoServer 2.21.0:\n\n1.  Navigate to **Security \u003e WPS Security** page\n2. Locate **Complex Inputs** heading\n3. Select the check box for **Disable loading complex inputs from remote references**\n\n### Resolution\n\nTo allow processing of complex inputs safely in GeoServer 2.22.5 and GeoServer 2.23.2:\n\n1. Navigate to **Security \u003e URL Checks**\n2. Enable **URL Checks** are enabled setting\n3. Check the user manual for [examples](https://docs.geoserver.org/latest/en/user/security/urlchecks.html#example-regex-patterns) of how to trust specific locations for your external services.\n\nProcessing of complex inputs safely is on by default in GeoServer 2.24.0.\n\n### References\n\n* [Complex Inputs](https://docs.geoserver.org/stable/en/user/services/wps/security.html#complex-inputs)\n* [URL Checks](https://docs.geoserver.org/latest/en/user/security/urlchecks.html)\n",
  "id": "GHSA-5pr3-m5hm-9956",
  "modified": "2023-10-27T21:04:48Z",
  "published": "2023-10-24T19:21:02Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/geoserver/geoserver/security/advisories/GHSA-5pr3-m5hm-9956"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-43795"
    },
    {
      "type": "WEB",
      "url": "https://docs.geoserver.org/latest/en/user/security/urlchecks.html"
    },
    {
      "type": "WEB",
      "url": "https://docs.geoserver.org/stable/en/user/services/wps/security.html#complex-inputs"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/geoserver/geoserver"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "WPS Server Side Request Forgery vulnerability"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.