Rackspace says an unauthorized party used leaked credentials to access parts of its Rackspace Spot cloud platform on November 17 and could read Kubernetes Secrets in some customer clusters. The intrusion was detailed in a customer notification obtained by BleepingComputer, which reported that the attacker could act as a legitimate user in some customer organizations.

The notification places the access window between approximately 00:20 and 22:00 UTC on November 17. Rackspace said the intruder could create pods in Kubernetes clusters, read Kubernetes Secrets, and list nodes and volumes. Secrets can contain passwords, authentication tokens and API keys used by applications to connect to databases, cloud services and other systems. Rackspace warned that any Secret in an affected user’s clusters, along with that user’s Spot API tokens and refresh tokens, could have been read.

Rackspace said it learned of the intrusion on November 18 after receiving a report from a customer and confirmed that the customer’s organization was affected the same day. The company said it revoked affected tokens and sessions, removed unauthorized pods, rotated keys, and strengthened access controls and monitoring. It also shared indicators of compromise with customers, including the IP address 23.224.79.106, the range 23.224.0.0/15, and suspicious Kubernetes pod or object prefixes beginning with i1, glm- and probe.

The incident also caused an extended outage of the Rackspace Spot administration console, temporarily preventing customers from managing clusters and rotating credentials that may have been exposed. Sirish Raghuram, co-founder and chief growth officer of Platform9, which co-developed Spot with Rackspace, said in a Reddit discussion quoted by BleepingComputer that the teams deliberately disabled access while sanitizing the environment. Rackspace announced that Spot service had been fully restored on November 21 after multiple delays.

READ
Kirsten Davies to Temporarily Lead US Cyber Office

Rackspace instructed affected customers to reissue Spot API tokens, replace refresh tokens used in automation tools, download fresh Kubernetes configuration files and rotate credentials stored in cluster Secrets. The company also advised reviewing logs for databases, container registries, Git repositories, cloud storage and third-party services dating back to November 17 to identify possible misuse of exposed credentials.

Rackspace has not disclosed how many customers were affected or whether information was actually stolen from the clusters. BleepingComputer said it asked the company about the scope of the incident and possible data theft but had not received a response at publication time.


Buy ExpressVPN with PayPal or Credit Card

The incident follows other reports of attackers reaching credentials stored in cloud environments, including the N-able Mail Assure credential exposure and the Qubole-linked intrusion into customer AWS environments.

Advertisement