Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Data accidentally exposed by Microsoft AI researchers

wiz.io

Post reply on HN
Print view View original

231–238 of 238 posts

Re: Data accidentally exposed by Microsoft AI researchers

#231

Post by tgsovlerkhgsel »

monkpit wrote: post #22
hdesh wrote: post #9

On a lighter note - I saw a chat message that started with "Hey dude! How is it going". I'm disappointed that the response was not https://nohello.net/en/ .

I strongly support the “no hello” concept but I also fear being seen as “that guy” so I never mention it. Sigh

"No hello" implies that people shouldn't be friendly at all, and comes across as rude.

The concept simply needs a more descriptive name to be accepted. It's not about not saying hello. It's about including the actual request in the first message, usually after the hello.

Re: Data accidentally exposed by Microsoft AI researchers

#232

Post by phatskat »

sillysaurusx wrote: post #167
trebligdivad wrote: post #73

Earlier quoted context omitted.

How would a pentest find that? Ok in this case it's splattered onto github; but the main point here is that you might have some unknown number of SAS tokens issued to unknown storage that you probably haven't any easy way to revoke.

A number of ways, including: - finding the token directly in the repo - reviewing all tokens issued

Did you read TFA? It does mention AI, and also mentions that this is less about AI and more about the fact that the AI researchers had a TON of data to share, and their method for doing so was poorly configured SAS tokens…

Which also, in the article, is mentioned can not be tracked - issued tokens happen on the client side (if I understood this correctly), which means that to audit tokens you’d have to ask everyone who had one issued to politely provide said token. Will everyone remember the tokens they have? Probably not. And if an attacker has already gotten what they needed, or managed to issue their own, no one would know.

Re: Data accidentally exposed by Microsoft AI researchers

#233

Post by permo-w »

mlyle wrote: post #229
permo-w wrote: post #227

Earlier quoted context omitted.

my mistake, I swapped the 38tb and 112tb from parent comment whatever the download size is, you're bottlenecked by the remote server's up speed

If the "remote server" is Azure, the target throughput is 0.5gbps ... for each large blob (of which this leak includes many). It seems pretty likely you'll be able to download at a few gigabits per second if your local connectivity allows.

that's a big if

Re: Data accidentally exposed by Microsoft AI researchers

#234

Post by mlyle »

permo-w wrote: post #233
mlyle wrote: post #229

Earlier quoted context omitted.

If the "remote server" is Azure, the target throughput is 0.5gbps ... for each large blob (of which this leak includes many). It seems pretty likely you'll be able to download at a few gigabits per second if your local connectivity allows.

that's a big if

We're talking about exfiltrating data from incorrect permissions on Azure, so it's not an if. It's a given for the situation in the article that we're discussing in this thread.

Re: Data accidentally exposed by Microsoft AI researchers

#235

Post by permo-w »

mlyle wrote: post #234
permo-w wrote: post #233

Earlier quoted context omitted.

that's a big if

We're talking about exfiltrating data from incorrect permissions on Azure, so it's not an if. It's a given for the situation in the article that we're discussing in this thread.

that's not quite true. the article discusses a transfer from Azure to Github. The article does not say where the files are currently hosted, besides being publicly available on Github. It's probably Azure, but it could easily also be whatever Github use

Re: Data accidentally exposed by Microsoft AI researchers

#236

Post by mlyle »

permo-w wrote: post #235
mlyle wrote: post #234

Earlier quoted context omitted.

We're talking about exfiltrating data from incorrect permissions on Azure, so it's not an if. It's a given for the situation in the article that we're discussing in this thread.

that's not quite true. the article discusses a transfer from Azure to Github. The article does not say where the files are currently hosted, besides being publicly available on Github. It's probably Azure, but it could easily also be whatever Github use

No, that is an incorrect reading of the article. A GitHub repository mentioned an Azure storage URL; that storage service was incorrectly configured-- exposing many sensitive blobs besides the one that was intended to be shared via the URL.

The URL was: "https\://robustnessws4285631339.blob.core.windows.net/public-models/robust_imagenet/resnet18_l2_eps3.ckpt?sv=2020-08-04&ss=bfqt&srt=sco&sp=rwdlacupitfx&se=2051-10-06T07:09:59Z&st=2021-10-05T23:09:59Z&spr=https,http&sig=U69sEOSMlliobiw8OgiZpLTaYyOA5yt5pHHH5%2FKUYgI%3D" (Backslash added to prevent HN from detecting it as an URL and shortening).

The issue was that "sig=U69s...." token gave access to far more than the researchers intended to share.

Re: Data accidentally exposed by Microsoft AI researchers

#237

Post by evntdrvn »

amlozano wrote: post #221
evntdrvn wrote: post #172

Earlier quoted context omitted.

what I always want to know when people talk about this is "what reputable companies can I actually pay to do a real pentest (without costing hundreds of thousands of dollars)."

The problem is security is a "Market for lemons" https://en.wikipedia.org/wiki/The_Market_for_Lemons . Just like when trying to buy a used car, you need someone who is basically an expert in selling used cars. In order to purchase a reputable pentest, you basically have to have a security team that is mature enough to have just done it themselves. I can throw out some names for some reputable firms, but you are still…

thank you!

Re: Data accidentally exposed by Microsoft AI researchers

#238

Post by permo-w »

mlyle wrote: post #236
permo-w wrote: post #235

Earlier quoted context omitted.

that's not quite true. the article discusses a transfer from Azure to Github. The article does not say where the files are currently hosted, besides being publicly available on Github. It's probably Azure, but it could easily also be whatever Github use

No, that is an incorrect reading of the article. A GitHub repository mentioned an Azure storage URL; that storage service was incorrectly configured-- exposing many sensitive blobs besides the one that was intended to be shared via the URL. The URL was: "https\://robustnessws4285631339.blob.core.windows.net/public-models/robust_imagenet/resnet18_l2_eps3.ckpt?sv=2020-08-04&ss=bfqt&srt=sco&sp=rwdlacupitfx&se=2051-10-06…

I stand corrected
Post reply on HN