News for hackers. Stuff that matters.
Re:Blocking Visual Studio Code embedded reverse shell before... by throwaway02y on Saturday September 23, 2023 @11:12AM (#37623979)
> internal network is now accessible from anywhere !

If you exposed it willingly.

Re:Blocking Visual Studio Code embedded reverse shell before... by taway1237 on Saturday September 23, 2023 @11:19AM (#37624043)
The point of the blog post is that this method is useful for attackers (as a so-called lolbin - trusted binary used in a malicious way).
Re:Blocking Visual Studio Code embedded reverse shell before... by baz00 on Saturday September 23, 2023 @11:12AM (#37623986)
I work with 500 idiots. Willingly and cluelessly are interchangeable.
Re:Blocking Visual Studio Code embedded reverse shell before... by eurg on Saturday September 23, 2023 @11:17AM (#37624032)
Not nicely put, but not wrong. I had half an heart attack when that feature was rolled out, and the danger was split only between myself and a colleague. I can't even trust myself to not screw up. I needed another permanencied invocation of the principle of hope.
Re:Blocking Visual Studio Code embedded reverse shell before... by intelVISA on Saturday September 23, 2023 @11:39AM (#37624245)
Well said, this is why working solo can be beneficial: only one idiot to look out for. :)
Re:Blocking Visual Studio Code embedded reverse shell before... by civilitty on Saturday September 23, 2023 @11:50AM (#37624350)
That’s the idiot that can do the most damage!
Re:Blocking Visual Studio Code embedded reverse shell before... by baz00 on Saturday September 23, 2023 @02:02PM (#37625711)
Can confirm.
Re:Blocking Visual Studio Code embedded reverse shell before... by eddythompson80 on Saturday September 23, 2023 @11:15AM (#37624011)
Take their computer away.
Re:Blocking Visual Studio Code embedded reverse shell before... by baz00 on Saturday September 23, 2023 @12:28PM (#37624723)
Management frowned at this suggestion.
Re:Blocking Visual Studio Code embedded reverse shell before... by Jochim on Saturday September 23, 2023 @01:56PM (#37625649)
Seems to be the goal of most "cybersecurity" types.
Re:Blocking Visual Studio Code embedded reverse shell before... by baz00 on Saturday September 23, 2023 @02:01PM (#37625700)
I thought their goal was collecting vendor certifications.
Re:Blocking Visual Studio Code embedded reverse shell before... by eddythompson80 on Saturday September 23, 2023 @02:04PM (#37625732)
Ouch dude
Re:Blocking Visual Studio Code embedded reverse shell before... by baz00 on Saturday September 23, 2023 @02:08PM (#37625770)
It's a burn but it's accurate. Had three consultancies in (high end well known ones) and and two in house certified to their eyeballs professional cyber security experts in charge. All they did was tick a fuck load of boxes, run some scans, spend a lot of money and make it really hard for people.

Yet I managed to find a fully remote RCE and exploit it in 30 minutes after they did all this.

The industry is a fucking scam.

Re:Blocking Visual Studio Code embedded reverse shell before... by rf15 on Saturday September 23, 2023 @04:34PM (#37627245)
Confirming this experience, it is Security Theatre all the way down.
Re:Blocking Visual Studio Code embedded reverse shell before... by Forbo on Sunday September 24, 2023 @12:45PM (#37634726)
Sounds like it's time to make your own certification. :D
Re:Blocking Visual Studio Code embedded reverse shell before... by userbinator on Saturday September 23, 2023 @01:42PM (#37625493)
The industry is only going to keep making more idiots if they treat developers like this.
Re:Blocking Visual Studio Code embedded reverse shell before... by baz00 on Saturday September 23, 2023 @02:01PM (#37625694)
It kept producing more idiots when we didn't treat them like this and this is easier so fuck it.