Re:Capital One Says Breach Hit 100M Individuals in U.S
by pmredux on Wednesday July 31, 2019 @02:21AM
(#20572092)
Might have been an SSRF exploit if the WAF was accepting parameter values that were then used to expose IAM credentials via the EC2 metadata service. See https://ejj.io/blog/capital-one for a good write-up.
Re:Capital One Says Breach Hit 100M Individuals in U.S
by samstave on Monday July 29, 2019 @08:13PM
(#20560882)
I wonder what data was in the bucket?
Re:Capital One Says Breach Hit 100M Individuals in U.S
by jlgaddis on Monday July 29, 2019 @08:37PM
(#20561013)
> The largest category of data stolen was supplied by consumers and small businesses when they applied for credit cards from 2005 through early 2019, the bank said. It included personal identification data, including names, addresses, phone numbers and dates of birth, and financial data including self-reported income, credit scores and fragments of transaction history.
> About 140,000 Social Security numbers were accessed, as well as 80,000 bank account numbers from credit-card customers, the bank said.
I haven't yet read (all of) the complaint but I presume it goes into even more detail than the article did.
Correction: according to the complaint, the defendant is alleged to have assumed an IAM role in the context of Capital One's account whose policy provided access to the S3 bucket in question. So it wasn't that the S3 bucket was public, but rather, that there was some vulnerability she took advantage of by which she obtained indirect credentials to it.
(Complaint, page 6, lines 14-27.)