Bunny CDN 安全事件
Bunny CDN Security Incident

原始链接: https://status.bunny.net/incidents/p6gf1by9kr7m

bunny.net 报告称,一家基础设施提供商发生了一起涉及第三方服务器管理软件的安全事件。亚美尼亚的一个 CDN 节点托管在受影响的提供商服务器上。收到警报后,bunny.net 在 20 分钟内停止了经由该服务器的流量路由,保存了日志,清空了服务器,撤销了其访问权限,并移除了该节点。bunny.net 和提供商均未发现服务器或节点被访问的证据,但无法完全排除未经授权的访问。如果发生了访问,可能暴露的数据包括临时缓存的 CDN 内容、Pull Zone 配置以及该节点上的 TLS 证书。作为预防措施,bunny.net 撤销并重新签发了所有平台 TLS 证书;托管的自定义域名证书重新签发正在进行中,预计将在 24 小时内完成,客户无需采取任何操作。自行管理 TLS 证书的客户应撤销并使用新的私钥重新签发证书。未影响其他客户数据或内部系统。bunny.net 将继续监控并提供更新。

Bunny.net 披露了一起安全事件,影响其托管于基础设施提供商的亚美尼亚 CDN 节点之一;该提供商报告称,第三方服务器管理软件存在未授权访问。Bunny 在 20 分钟内停止经该节点路由流量,保存日志,擦除服务器,撤销其访问权限并移除该节点。它称该服务器上的缓存 CDN 内容、Pull Zone 配置和 TLS 证书可能已暴露,但未发现未授权访问证据。Bunny 已吊销并重新签发其自有平台证书,并正在重新签发托管客户证书;使用自管理证书的客户应吊销并重新签发这些证书。没有其他客户数据或内部系统受到影响。Hacker News 评论者大多称赞 Bunny 的快速响应,同时争论证书轮换意味着实际入侵还是预防性风险管控。有人指出提供商可能是 Gcore,对其与俄罗斯的关联表示担忧,并批评外包及事件响应实践。其他人表示此类事件日益常见。
相关文章

原文
We're reaching out to inform you of a security incident involving one of our infrastructure providers, the steps we've taken, and what this means for you.

- What happened and how we responded

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.

Our investigation found no evidence of unauthorized access to the CDN node or any of its data. The infrastructure provider has also found no evidence that our server was accessed, but continues to investigate the incident.

- What this means for your data

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.

- What happens next

We’re closely monitoring our infrastructure and working with the affected provider as the investigation continues. Should any new findings affect our customers, we will provide an update via email and on our status page.

At bunny.net, we understand the trust you place in us to keep your content secure, and we take that responsibility seriously. If you have any questions or need help with managing your TLS certificates, our support team will be happy to assist.

联系我们 contact @ memedata.com