Live data from Hacker News

A supply chain attack on PyTorch

johnstawinski.com

1–10 of 109 posts

Re: A supply chain attack on PyTorch

#2
Among other nice things, I liked

> We used our C2 repository to execute the pwd && ls && /home && ip a command on the runner labeled “jenkins-worker-rocm-amd-34”, confirming stable C2 and remote code execution. We also ran sudo -l to confirm we had root access.

While it's not clear was it curated list of commands or just ALL, I assume the latter and that makes me feel no system administrator was involved into that pipelines setup - those guys are quite allergic to giving sudo/root access at all

Re: A supply chain attack on PyTorch

#5
I know that it is zeitgeist exploiting to say this, but seeing Boeing listed and not Airbus really says something to me.

Lockheed being listed makes me wonder if the FBI/CIA really will (further) step up on cybercrime, because you now have potential national security implications in a core supplier to multiple military branches.

Re: A supply chain attack on PyTorch

#6
post #3

Is 5k an appropriate amount for such a finding? Sounds incredibly cheap for such a large organization. How much would something like this be worth on the black market?

you have to consider that in the black market the rates would absorb the illegality of the action. while 5k is 'clean'

Re: A supply chain attack on PyTorch

#7
post #3

Is 5k an appropriate amount for such a finding? Sounds incredibly cheap for such a large organization. How much would something like this be worth on the black market?

you have to consider that in the black market the rates would absorb the illegality of the action. while 5k is 'clean'

Monero is always clean, too.

Re: A supply chain attack on PyTorch

#9
post #3

Is 5k an appropriate amount for such a finding? Sounds incredibly cheap for such a large organization. How much would something like this be worth on the black market?

No, that is in general the issue with security bounties. They attract mainly people who have enough time for trial and error and/or prior domain expertise and/or extremely smart in specific software. Nowadays cybersecurity is a vast field and it is not the same to be a white hat hacker specialized in Google Chrome issues than one in iOS. Not saying it cannot be the same person but the amount of time required to catch issues is long.

I think supply chain attacks are not being taken very seriously. Think that people working, for example, in Python or JavaScript use pip or npm daily no matter if they work for a nuclear agency or your uncle's bar.

Re: A supply chain attack on PyTorch

#10

Hm, from the reading, it seem he was pretty careful to not do any harm, but still, is this type of practical research actually legal?

It depends on the company. Many companies have bug bounty or vulnerability disclosure programs that explicitly guarantee safe harbor+protections for researchers.

However, not all organizations are happy to be contacted about security issues. Sometimes doing the right thing can still result in (threats of) legal repercussions.

https://arstechnica.com/tech-policy/2021/10/missouri-gov-cal...

Post reply on HN