Bunny.net pulls a CDN node in Armenia after its hosting provider was breached
Bunny CDN Security Incident
Bunny.net says one of its infrastructure providers suffered unauthorized access through third-party server management software, and that a CDN node in Armenia ran on an affected server. Engineers cut traffic within 20 minutes, wiped the machine, and revoked its access. Neither investigation found evidence of a breach, but cached content, Pull Zone configs, and TLS certificates could have been exposed, so the company reissued all platform certificates and is finishing managed custom-domain certs.
While neither investigation has found any indication of unauthorized access to our server, we cannot completely rule out the possibility.
- colonCapitalDee
Prompt and competent response, as expected from bunny.
"Last week, one of our infrastructure providers reported unauthorized access involving third-party server management software. One of our CDN nodes, located in Armenia, was hosted on a server supplied by this provider.
After receiving the alert from the affected provider, our engineering team took immediate action. Within 20 minutes, we stopped routing traffic through the server. We then reviewed and preserved the relevant security logs for investigation, securely wiped the server, and revoked its access to our other systems. The affected server has been permanently removed from our infrastructure."
- eraclide
Bunny used Gcore in Armenia. Gcore themselves got hacked, not Bunny. Bunny was just an affected downstream, in only one of their POPs.
https://lowendtalk.com/discussion/222315/gcore-compromised-v...
The title is heavily misleading.
- bobtheborg
While neither investigation has found any indication of unauthorized access to our server, we cannot completely rule out the possibility.
If unauthorized access to our CDN node did occur, the potentially exposed information would have been: temporarily cached CDN content, Pull Zone configurations, and TLS certificates stored on that server.
As an additional precaution, we have revoked and reissued all TLS certificates for bunny. net platform domains (b-cdn. net and bunny. run). Reissuance of managed TLS certificates for custom domains is ongoing and is expected to be completed within the next 24 hours. No action is required from customers using managed certificates. We will post a further update on our status page once this process is complete.
If you manage your own TLS certificates, we recommend revoking and reissuing them with new private keys as a precaution.
No other customer data, including bunny. net account data, was stored on the server in question, and no internal systems were affected.
so it seems like the underlying provider potentially allowed, for instance, disk read, that above is what bunny says might have been on disk in this case? Am I reading that right?
- evan_a_a
> After receiving the alert from the affected provider, our engineering team took immediate action. Within 20 minutes, we stopped routing traffic through the server. We then reviewed and preserved the relevant security logs for investigation, securely wiped the server, and revoked its access to our other systems. The affected server has been permanently removed from our infrastructure.
When responding to a potential breach, the correct protocol is to contain the incident and PRESERVE EVERYTHING for investigation. Do not try to be selective at what data you keep or don't keep. They've unfortunately likely destroyed evidence and will not be able to determine if the attacker actually breached the server or not, and if so, how. This speaks to them having a poor or non-existent incident response plan.
- bitlad
It feels like theres an incident every hour.