Malware
Cisco Ensures DevHub Site Leak Won’t Empower Future Breaches
Cisco has assured customers that a recent data leak from its DevHub site will not enable future cyber breaches. The leak exposed sensitive information, including users’ API keys, but Cisco has taken the necessary steps to mitigate the potential risks and protect its users’ security.
Recently, a threat actor managed to download non-public files from a misconfigured public-facing DevHub portal. Although this sounds alarming, we want to reassure you that the exposed documents do not contain information that could be exploited in future breaches of our systems.
What exactly was exposed?
Upon analyzing the exposed documents, we found that their contents include data that we publish for customers and other DevHub users. However, files that shouldn’t have been made public were also available, some belonging to CX Professional Services customers.
“So far, in our research, we’ve determined that a limited set of CX Professional Services customers had files included and we notified them directly,” we said.
Our teams have worked diligently to assess the content of those files. We want to emphasize that we have not identified any information in the content that an actor could have used to access any of our production or enterprise environments.
What actions have we taken?
We have since corrected the configuration and restored public access to the DevHub site. Additionally, we’ve confirmed that web search engines did not index the exposed documents.
This update comes after we confirmed last month that we took our public DevHub site offline (a resource center for customers where we publish software code, templates, and scripts) after a threat actor leaked what we described at the time as “non-public” data.
It’s important to note that we found no evidence that any financial data or personal information had been exposed or stolen from the public DevHub portal before it was taken offline.
What about the alleged access to a developer environment?
The threat actor behind the leak, IntelBroker, claimed that they also gained access to a Cisco JFrog developer environment through an exposed API token. While we maintain that our systems haven’t been breached, information shared by the threat actor indicates that they also breached a third-party development environment, allowing them to steal data.
We’ve been contacted with further questions about IntelBroker’s claims, but we have not replied as of yet.
What’s the takeaway from all of this?
While the exposure of non-public files is a concern, we want to reiterate that the information contained within those files does not put our systems at risk for future breaches. We have taken the necessary steps to correct the configuration issues and restore access to our DevHub site, ensuring that such an incident doesn’t occur again.
As always, your security is our top priority. We encourage you to reach out to us with any questions or concerns, and keep coming back to learn more about how we’re working to protect your data and keep you safe.