GeoServer Blog

GeoServer 2.20.3 Released

Mar 8, 2022 • Jody Garnett

GeoServer 2.20.3 release is now available with downloads (bin, war, windows), along with docs and extensions.

This is a stable release of the 2.20.x series recommended for production systems. This release was made in conjunction with GeoTools 26.3.

Thanks to everyone who contributed, and to Jody Garnett (GeoCat) for making this release.

Security Considerations

This release includes several security enhancements and is a recommended upgrade for production systems.

This release includes two improvements limiting Server-side request forgery (SSRF) opportunities:

We would like to thank GeoCat for addressing these two issues on behalf of Fisheries and Oceans Canada. If you wish to report a security vulnerability, please visit our website for instructions on responsible reporting.

Improvements and Fixes

Improvements:

  • GEOS-10367 Allow GetTimeSeries to have a maximum times limit separate than WMS max dimensions

Fixes:

  • GEOS-10379 WCS 2.0 requested ScaleSize not being respected when crossing the dateline

  • GEOS-10377 Layers and Layer Groups get default abstract in capabilities document when none set in configuration.

  • GEOS-10373 GetTimeSeries does not work on source data with time ranges

  • GEOS-10362 Username remains in roles.xml after user removal operation

  • GEOS-10316 Regression in 2.20.x: Unable to specify JAVA_OPTS for startup.sh

  • GEOS-10066 CSS ArrayList class cast exception in layer rendering

  • GEOS-9785 Invalid argument type=null when trying to use gs:Download WPS identifier

  • GEOS-9770 Cascading WMS server sets invalid I and J when using EPSG:3006 on GetFeatureInfo calls

For more information see 2.20.3 release notes.

About GeoServer 2.20

Additional information on GeoServer 2.20 series:

Release notes: ( 2.20.3 | 2.20.2 | 2.20.1 | 2.20.0 | 2.20-RC )

Read More

GeoServer 2.19.5 Released

Mar 8, 2022 • Ian Turton

The GeoServer team are happy to announce GeoServer 2.19.5 release is available for download (zip and war) along with docs and extensions.

This GeoServer 2.19.5 release was produced in conjunction with GeoTools 25.5 and GeoWebCache 1.19.2, this is a maintenance release recommended for production systems.

Thanks to everyone who contributed, and to Ian Turton (Astun Technology) for making this release.

Security Considerations

This release includes several security enhancements and is a recommended update for production systems.

This release includes two improvements limiting Server-side request forgery (SSRF) opportunities:

We would like to thank GeoCat for addressing these two issues on behalf of Fisheries and Oceans Canada. If you wish to report a security vulnerability, please visit our website for instructions on responsible reporting.

Improvements and Fixes

Fixes:

  • GEOS-9785 Invalid argument type=null when trying to use gs:Download WPS identifier
  • GEOS-9770 Cascading WMS server sets invalid I and J when using EPSG:3006 on GetFeatureInfo calls

About GeoServer 2.19

Additional information on GeoServer 2.19 series:

Release notes ( 2.19.5 | 2.19.4 | 2.19.3 | 2.19.2| 2.19.1 | 2.19.0 | 2.19-RC )

Read More

GeoServer 2.20.2 Released

Jan 24, 2022 • Jody Garnett

We are happy to announce GeoServer 2.20.2 release is available with downloads (bin, war, windows), along with docs and extensions.

This is a stable release of the 2.20.x series recommended for production systems. This release was made in conjunction with GeoTools 26.2 and GeoWebCache 1.20.1.

Security Considerations

This release includes several security enhancements and is a recommended upgrade for production systems:

  • GeoServer uses the earlier log4j1 library and is not subject to the Log4j2 remote code execution vulnerabilities reported worldwide. For a detailed discussion please read GeoServer Log4J2 zero day vulnerability assessment.

    The release of GeoServer includes a patched version of log4j1 which does not include any remote loggers or socket communication.

If you wish to report a security vulnerability, please visit our website for instructions on responsible reporting.

Mark Factory Precedence

When rendering maps with lots of individual graphics, looking up the correct implementation (known as a MarkFactory) can be time consuming.

WMS Settings have new capability to filter out any mark factories not being used, and provide an order to prioritise the ones being used.

For more information see WMS Web Administration (user guide).

Source Code

For developers building from source, we have committed a .gitattributes file to help preserve consistent line encoding across our repository.

With this change it is no longer necessary to set your global configuration to core.autocrlf=input.

Use git reset as outlined below if encounter difficulty updating your checkout:

git pull --rebase
git reset --hard

Improvements and Fixes

  • WMS rendering preserves region of interest when clipping working with palette based images
  • Importer improvements to better report failed imports and clean up stale importer contents
  • WCS return coverages whose native BBOX are slightly outside of the dateline
  • Reduce the CPU load of returning Server Status information using OSHI on windows

For more information see 2.20.2 release notes.

About GeoServer 2.20

Additional information on GeoServer 2.20 series:

Release notes: ( 2.20.2 | 2.20.1 | 2.20.0 | 2.20-RC )

Read More

Log4j1 update or replace activity

Jan 20, 2022 • Jody Garnett

While GeoServer is not vulnerable to Log4J2 Log4Shell vulnerability, we would like to thank everyone who has reached out with offers of concern and assistance.

The Log4J 1.2 library used by GeoServer has a number of smaller vulnerabilities which we would like to address. While the GeoServer default configuration is not vulnerable it is time to upgrade or replace this library. If you are at all concerned, locate WEB-INF/lib/log4j-1.2.17.jar and replace with our custom log4j-1.2.17.norce.jar, and restart GeoServer.

The GeoSever Project Steering Committee invites:

  • Proposals for updating or replacing the Log4J1 library used by GeoServer.

    Successful proposals should consider changes required to GeoTools logging (which bridges from java utility logging to selected logging library), integration with GeoWebCache (uses apache-commons-logging to delegate to selected logging library), and GeoServer (which allows users to select different logging profiles without restarting the application).

  • Sponsors interested in funding this activity as a security concern.

    Organizations running GeoServer in a cloud environment are also encouraged to fund this activity. The leading contenders (log4j2,logback,java util logging) provide better integration with cloud logging services than the log4j1 library presently used.

This is a time sensitive activity as we would like to select a good proposal and see the result implemented for the upcoming GeoServer 2.21-RC Release Candidate in March.

Thanks to activity sponsors for your support:

For more information visit updating or replacing the Log4J1 wiki page.

Read More

GeoServer 2.19.4 Released

Dec 22, 2021 • Andrea Aime

The GeoServer team are happy to announce GeoServer 2.19.4 release is available for download (zip and war) along with docs and extensions.

This GeoServer 2.19.4 release was produced in conjunction with GeoTools 25.4 and GeoWebCache 1.19.2, this is a maintenance release recommended for production systems.

Thanks to everyone who contributed, and to Andrea Aime (GeoSolutions) for making this release.

Security Considerations

This release includes several security enhancements and is a recommended upgrade for production systems:

  • GeoServer uses the earlier log4j1 library and is not subject to the Log4j2 remote code execution vulnerabilities reported worldwide. For a detailed discussion please read GeoServer Log4J2 zero day vulnerability assessment.

    The release of GeoServer includes a patched version of log4j1 which does not include any remote loggers or socket communication.

If you wish to report a security vulnerability, please visit our website for instructions on responsible reporting.

Improvements and Fixes

Bug

  • GEOS-10337 Harden importer against failed imports, make failures more evident

  • GEOS-10322 JDBCConfig community module does not deal with stale connections to the database

  • GEOS-10300 The map preview logs errors when using AUTO codes

  • GEOS-10299 The reprojection console does not work with AUTO codes

  • GEOS-10292 Changing worker pool size in raster access is not actually applied (silent error)

  • GEOS-10289 GeoServer busy for 1 hour on reloading a 50000 shapefiles Directory datastore

  • GEOS-10281 GeoServer log level not picked up with Catalog reload

  • GEOS-10249 GWC produce NPE when it comes to race condition

Improvement

  • GEOS-10328 Expire completed and stale importer contexts

  • GEOS-10321 WCS 2.0 might fail to return coverages whose native BBOX goes slighly outside of the dateline

  • GEOS-10315 Features Templating - Allow injecting JSON-LD output in HTML

  • GEOS-10314 Features Templating - allow specifying root @type in the JSON-LD output and a different name for features array

GEOS-9904 GeoFence backend DBMS dependencies

Task

  • GEOS-10335 Update GeoServer to a log4j version that does not support RCEs

  • GEOS-10269 Overriding JSON Object while Merging Feature Templates

  • GEOS-10268 Null Support in Features Templating

About GeoServer 2.19

Additional information on GeoServer 2.19 series:

Release notes ( 2.19.3 | 2.19.2| 2.19.1 | 2.19.0 | 2.19-RC )

Read More

 Announcements

 Behind The Scenes

 Tutorials

 Vulnerability

 Developer notes