Last month, we released Grafana 6.1.5, which included an important security fix. We want to share with you the backstory.
We all make mistakes, and this time the mistake was mine.
In the 5.3.3 security release, we forgot to merge the patch back to master, which means all releases between 5.3.3 and 6.1.4 still contained the vulnerability. We later discovered our oversight, fixed it, and released a new patch on April 29.
Since this mistake was caused by our process, we are publishing an incident review about it. The document provides a timeline for what happened, the contributing factors for the oversight, and action items for establishing a security release plan going forward.
Hopefully this can be a valuable lesson for others as well. If you have any feedback, please let us know.
Reporting Security Issues
If you think you have found a security vulnerability, please send a report to firstname.lastname@example.org. This address can be used for all of Grafana Labs’s open source and commercial products (including but not limited to Grafana, Grafana Cloud, Grafana Enterprise, and grafana.com). We can accept only vulnerability reports at this address. We would prefer that you encrypt your message to us; please use our PGP key. The key fingerprint is:
F988 7BEA 027A 049F AE8E 5CAA D125 8932 BE24 C5CA
The key is available from pgp.mit.edu by searching for grafana.
We maintain a category on the community site called Security Announcements, where we will post a summary, remediation, and mitigation details for any patch containing security fixes. You can also subscribe to email updates to this category if you have a grafana.com account and sign on to the community site or track updates via an RSS feed.