Skip to content

Latest commit

 

History

History
58 lines (36 loc) · 3.15 KB

SECURITY.md

File metadata and controls

58 lines (36 loc) · 3.15 KB
Raw

Security Policy

Supported Versions

Each GeoServer release is supported with bug fixes for a year, with releases made approximately every two months.

Version Supported Available
stable ✅ six months
maintenance ✅ twelve months
archived ❌

This approach provides ample time for upgrading ensuring you are always working with a supported GeoServer release.

If your organisation is making use of a GeoServer version that is no longer in use by the community all is not lost. You can volunteer on the developer list to make additional releases, or engage with one of our Commercial Support providers.

Reporting a Vulnerability

If you encounter a security vulnerability in GeoServer please take care to report in a responsible fashion:

  1. Keep exploit details out of public mailing lists and issue tracker.

  2. There are two options to report a security vulnerability:

    • To report via email:

      Please send an email directly to the volunteers on the private geoserver-security@lists.osgeo.org mailing list. Provide information about the security vulnerability you might have found in your email.

      This is a moderated list: send directly to the address; your email will be moderated; and eventually shared with volunteers.

    • To report via GitHub:

      Navigate to security page, use link for Private vulnerability reporting.

      For more information see GitHub documentation.

  3. There is no expected response time. Be prepared to work with geoserver-security email list volunteers on a solution.

  4. Keep in mind participants are volunteering their time, an extensive fix may require fundraising/resources.

For more information see Community Support.

Coordinated vulnerability disclosure

Disclosure policy:

  1. The reported vulnerability has been verified by working with the geoserver-security list
  2. GitHub security advisory is used to reserve a CVE number
  3. A fix or documentation clarification is accepted and backported to both the "stable" and "maintenance" branches
  4. A fix is included for the "stable" and "maintenance" downloads (released as scheduled, or issued via emergency update)
  5. The CVE vulnerability is published with mitigation and patch instructions

This represents a balance between transparency and particpation that does not overwhelm particpants. Those seeking greater visibility are encouraged to volunteer with the geoserver-security list; or work with one of the commercial support providers who participate on behalf of their customers.