Bunny.net extends TLS certificate reissuance estimate after infrastructure provider breach
Bunny.net has replaced platform certificates and expects managed customer certificate reissuance to finish October 31st. Neither investigation has found evidence that its Armenia node was accessed.
By Ryan Merket · Published
Primary source: Hacker News
Why it matters
A compromised CDN edge node can expose cached content, zone configurations, and TLS keys for the sites it serves. Bunny.net said the Armenia node sat on a server supplied by one of its infrastructure providers, so customers depended on Bunny.net's response to unauthorized access reported by that provider.
Bunny.net, led by founder and CEO Dejan Grofelnik Pelzel, is reissuing managed customer TLS certificates as a precaution after an infrastructure provider reported a breach. In its October 28th status update, posted at 11:40 UTC, Bunny.net said one of its infrastructure providers had reported unauthorized access involving third-party server management software, and that one Bunny.net CDN node in Armenia sat on a server supplied by that…
When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.