CVE-2023-25157

CVE-2023-25157 is a critical-severity SQL injection vulnerability in org.geoserver.community:gs-jdbcconfig (maven), affecting versions < 2.21.4. It is fixed in 2.21.4, 2.22.2.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

GeoServer OGC Filter SQL Injection Vulnerabilities

Workarounds

  1. Disabling the PostGIS Datastore encode functions setting to mitigate strEndsWith, strStartsWith vulnerabilities (Like filters have no mitigation, if there is a string field in the feature type published).
  2. Enabling the PostGIS DataStore preparedStatements setting to mitigate the FeatureId vulnerability.

References

Impact

GeoServer includes support for the OGC Filter expression language and the OGC Common Query Language (CQL) as part of the Web Feature Service (WFS) and Web Map Service (WMS) protocols. CQL is also supported through the Web Coverage Service (WCS) protocol for ImageMosaic coverages.

SQL Injection Vulnerabilities have been found with:

  • PropertyIsLike filter, when used with a String field and any database DataStore, or with a PostGIS DataStore with encode functions enabled
  • strEndsWith function, when used with a PostGIS DataStore with encode functions enabled
  • strStartsWith function, when used with a PostGIS DataStore with encode functions enabled
  • FeatureId filter, when used with any database table having a String primary key column and when prepared statements are disabled
  • jsonArrayContains function, when used with a String or JSON field and with a PostGIS or Oracle DataStore (GeoServer 2.22.0+ only)
  • DWithin filter, when used with an Oracle DataStore

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

CVE-2023-25157 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.21.4, 2.22.2); upgrading removes the vulnerable code path.

Affected versions

org.geoserver.community:gs-jdbcconfig (< 2.21.4) org.geoserver.community:gs-jdbcconfig (>= 2.22.0, < 2.22.2)

Security releases

org.geoserver.community:gs-jdbcconfig → 2.21.4 (maven) org.geoserver.community:gs-jdbcconfig → 2.22.2 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

  • GeoSever 2.21.4
  • GeoServer 2.22.2
  • GeoServer 2.20.7
  • GeoServer 2.19.7
  • GeoServer 2.18.7

Frequently Asked Questions

  1. What is CVE-2023-25157? CVE-2023-25157 is a critical-severity SQL injection vulnerability in org.geoserver.community:gs-jdbcconfig (maven), affecting versions < 2.21.4. It is fixed in 2.21.4, 2.22.2. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
  2. How severe is CVE-2023-25157? CVE-2023-25157 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of org.geoserver.community:gs-jdbcconfig are affected by CVE-2023-25157? org.geoserver.community:gs-jdbcconfig (maven) versions < 2.21.4 is affected.
  4. Is there a fix for CVE-2023-25157? Yes. CVE-2023-25157 is fixed in 2.21.4, 2.22.2. Upgrade to this version or later.
  5. Is CVE-2023-25157 exploitable, and should I be worried? Whether CVE-2023-25157 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2023-25157 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2023-25157?
    • Upgrade org.geoserver.community:gs-jdbcconfig to 2.21.4 or later
    • Upgrade org.geoserver.community:gs-jdbcconfig to 2.22.2 or later

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo