I find it really baffling how much they are downplaying this incident on their statement.
”An external incident response firm reviewed PingCAP’s production systems and found no evidence that the attacker ran commands or maintained persistent access in the systems reviewed”
That does not appear to be true.
im not an expert but if I was an investor I'd try to find a buyer for my shares and run
is load bearing I expect.
Holy hell, I've heard of this happening, but I've never personally seen it in my 10 years as an SRE. That's absolutely wild.
[1]https://www.pingcap.com/press-release/tidb-ncc-group-securit...
It looks like you can assess the hell out of your source code, but your system can still leak if you don't secure your operations.
"good opsec will save you from bad crypto. but the converse is not true, good crypto will not save you from bad opsec"
> We even stood up a replication feed of their own control-plane database using credentials committed in their own repositories — GCP service-account keys and an Azure service principal — and let their infrastructure deliver it to us. Every six hours, for the last twenty-two days of the campaign, from 8 September to 30 September, that pipeline faithfully re-exported every table of the operational heart of TiDB Cloud — tenants, users, API keys, cluster credentials, changefeeds, migrations — and pushed it out.
With support from outside counsel and third-party forensic specialists, there is no evidence that data stored in TiDB was impacted. We keep on investigating and will provide updates on any new findings.
But what matters is that it was all memory safe and had no data races.
and how are people not talking about this more