[Geoserver-users] GeoServer 2.9.1 Released!

GeoServer GeoServer User
1

Hi everyone,

Apologies for the delay on the release announcement email! Thanks to Ben for the edits to the blog post.

The GeoServer team is pleased to announce the release of GeoServer 2.9.1. Download bundles are provided (bin, war, dmg and exe) along with documentation and extensions.

GeoServer 2.9.1 is the latest stable release of GeoServer and is recommended for production deployment. This release is made in conjunction with GeoTools 15.1 and GeoWebCache 1.9.1. Thanks to all contributors. Fixes and new functionality include:

  • Security enhancements: this release is a recommended upgrade (see Security Considerations below for details)
  • Fixes for WFS editing failing for geometries in full 3D CRS
  • ColorMap variable substitution now working correctly for multiple layers in a GetMap request
  • PDF printing fixed to properly render SLD “shape://horline” symbol, prevent invalid polygon generation, out of memory errors, and large file generation.
  • Integrated GeoFence DB path is now set correctly in Windows.
  • KML placemarks now being set correctly when KMSCORE=0
  • Support for rotated pole projection NetCDF and GRIB2 files, including the native GRIB2 file format used by the NOAA Rapid Refresh (RAPv3) weather forecast model
  • Support for multivalued xlink:href ClientProperty in app-schema mappings
  • Support requiring files to exist for GeoServer startup, to protect against insecure fallback when a data directory on a network share is unavailable
  • And much more, see all the tickets resolved in the release notes

This release has been made by Devon Tucker (Boundless) with help and encouragement from the GeoServer community.

Security Considerations

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

  • A remote execution vulnerability has been reported against both the Restlet library and the Apache Commons BeanUtils library, which is used by a number of facilities including our JSON parser. While we have not been able to demonstrate any way to exploit these vulnerabilities, we have patched our use of these libraries as a preventative measure. We would like to thank Kevin Smith for doing the bulk of the work, and Andrea Aime for providing a patched BeanUtils library addressing these vulnerabilities.
  • Layer security restrictions in CHALLENGE mode were not being correctly applied by embedded GeoWebCache. Thanks to Nick Muerdter for his responsible report of this vulnerability and for submitting a fix that included a unit test.
  • Carl Schroedl reported a vulnerability at application startup when working with a data directory on a network file system: if the network file system is not available at startup, GeoServer may fall back to its default insecure configuration. We have added a GEOSERVER_REQUIRE_FILE parameter to require the presence of one or more files during startup to defend against this situation. Thanks to Carl for following our responsible disclosure procedure, and to Ben Caradoc-Davies for implementing the new parameter.

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

About GeoServer 2.9

Articles, docs, blog posts and presentations: