Bunny CDN Security Incident

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."

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.

It feels like theres an incident every hour.

  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.

php.net is on Bunny to my knowledge and so is PECL for example. Great potential for compromised packages if this hadn't been caught , but I don't know the blast radius since the victim would need to connect to this particular CDN

Sadly this is entirely predictable.

Some time ago my colleague and I were doing some due-diligence on Bunny as a potential service provider.

We asked them some basic security questions, nothing low-level, just some basic high-level overview type of stuff to roughly check if they were following well-known best-practices.

Their response was a consistent and constant "cannot tell you due to security reasons".

That rang alarm bells. Any provider such as them who is not sufficiently confident in their security to be willing and able to discuss security at a high-level perspective is not worthy of trust as far as I am concerned.

[flagged]