NHacker Next on Rails
  • top
  • new
  • best
  • ask
  • show
  • jobs
login
GuidelinesFAQListsAPISecurityLegalApply to YCContact

Hacker News on Rails, powered by React on Rails Pro. Open the source on GitHub by ShakaCode.

Commit 06fc0df

Rendered at 09:12:22 GMT+0000 (Coordinated Universal Time) with Rails + React on Rails RSC.

PingCap TiDB Leaks (fulcrumsec.vg)

108 points by swyx 10h ago | 14 comments

xKingfisher 3h ago
Coming this close on the heels of the security audit by NCC [1] is pretty embarassing for all parties.

[1]https://www.pingcap.com/press-release/tidb-ncc-group-securit...

arpinum 9h ago
AWS private rates gives PingCAP ~47% off list price. Wonder which services got the biggest discounts? Unsurprisingly for a db company the cross-az traffic is 15% of their bill.
nemothekid 4h ago
Man I recently executed a migration from Aurora to Planetscale. I seriously considered PingCap but decided against it because I thought they cloud pricing was too complex. I wonder if my personal information is in the leak.
dherls 5h ago
If true, this is next level incompetence from PingCap. Apparently the attackers set up a replication pipeline for a month?!

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

wannabe44 2h ago
> Summary: "The root password of the cluster can be reset unconditionally"

But what matters is that it was all memory safe and had no data races.

dangoodmanUT 6h ago
what is happening today

and how are people not talking about this more

dilyevsky 3h ago
only the beginning. next year or two are going to be wild on this front so buckle up...
esafak 3h ago
https://www.moxfive.com/blog/who-is-fulcrumsec-inside-the-cl...
rvz 10h ago
First the Google Cloud outage [0], then the CA private key leak [1]...

...and now this...

> Today we are making the PingCAP breach public. We possess the complete TiDB Cloud control plane, its billing and finance estate, its GCP storage estate and its AWS cost and billing estate, its Jira, its CRM, its analytics, its source code, and a four-year log of every connection every customer ever made to its product, from the IP addresses of their application servers.

This is an entire leak of ALL PingCap TiDB's customers AND data.

All of this in a single day. It is over.

[0] https://news.ycombinator.com/item?id=50163961

[1] https://news.ycombinator.com/item?id=50166579

gregwebs 5h ago
I am reading this as a leak of every possible piece of metadata but not an actual leak of customer data. They have SQL logs which do contain customer data and there is a mention of some snapshots/imports.
hdjdnxjzhzhs 5h ago
How the fuck is 10.6TB metadata?
gregwebs 4h ago
TiDB is for large scale data. You generally wouldn't use it unless you have at least 1TB of data. 10TB is a single small customer database for them.
binsquare 5h ago
Easily at scale

Size is not a good indicator for content quality

qingcharles 5h ago
Don't forget the PHP megabomb dropping in a few hours too.