News for hackers. Stuff that matters.
Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by yunesj on Saturday May 23, 2020 @12:54PM (#23284467)
> It's important to note the nature of the failure.

Definitely! UCSF had a security firm send out a fishy-looking fishing email. My email client pointed out the url did not match the link text, whois told me it was a security company, and I opened the URL in a VM.

“You just got fished!” eye roll

I wouldn’t be surprised if most of those employees at gitlab were not so much fished as curious.

Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by dyslexit on Saturday May 23, 2020 @01:27PM (#23284742)
The article says 17 employees opened the link, and 10 of those types in their credentials. The 20% the headline is talking about are those 10, not the 7 that didn't do anything.
Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by paholg on Saturday May 23, 2020 @05:53PM (#23286861)
They did a test like this at a company I worked at. I ended up entering fake credentials because the thing seemed so shady, I was curious what its deal was.
Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by mcny on Saturday May 23, 2020 @06:57PM (#23287355)
I opened the email and I forwarded the email to abuse at corporate domain just like the corporate website says and my manager still got an email saying I failed the test.

Maybe because the tracking pixel remote image loaded? I remember reading an article where people sent an email to Apple and it got passed around within Apple and iirc either Steve Jobs or someone who reports directly to Steve Jobs opened the email not knowing that they were sending out a makeshift read receipt every time they opened the email.

Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by yosito on Saturday May 23, 2020 @08:40PM (#23288036)
Hi Gitlab! I'm available for hire if you need a replacement.
Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by pdonis on Saturday May 23, 2020 @02:29PM (#23285216)
> I wouldn’t be surprised if most of those employees at gitlab were not so much fished as curious.

"Curious" might get you to opening the web page, but actually entering credentials moves you into "phished" no matter how curious you are.

Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by TimTheTinker on Saturday May 23, 2020 @06:13PM (#23287014)
Not if every component is intentionally faked.
Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by pdonis on Saturday May 23, 2020 @07:22PM (#23287540)
I'm not even going to get to the point of wondering whether every component is faked or not, since my thought process will stop at "I'm not going to ever enter credentials into a site I got to from a random link in an email". Which seems to me to be a far better policy than trying to figure out whether a particular site I got to from a random link in an email is faked or not.
Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by kba on Saturday May 23, 2020 @09:55PM (#23288426)
Nobody is demanding you do. But if you go around claimng people "got phished", then you should be sure.

I've also entered fake credentials into a clearly faked login form to see what'd happen. Would it redirect me to the right site? Just claim the information was wrong? Send me to a mock up of the intranet I was trying to access? You can call it bad policy if you want (although you don't know about my precautions), but it doesn't mean I was phished.

Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by bitdeveloper on Sunday May 24, 2020 @12:17AM (#23289035)
What it does mean, though, is the person who sent the email now knows, at the minimum:

1. Someone receives and reads the email sent to this email address.

2. That person is willing to enter data into a form.

This is 2 pieces of information the person didn’t have before, and it can be used in further phishing attempts in a variety of ways.

It doesn’t mean you were fooled, but that’s only half the story.

Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by zifnab06 on Saturday May 23, 2020 @03:27PM (#23285653)
I did the same thing at a previous job. Got signed up for an 8 hour security training because of it - somehow I refused to go and they didn't fire me.
Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by leppr on Saturday May 23, 2020 @01:01PM (#23284527)
VM escape exploits are a actually used in the wild, so yes, if that was on your work machine, you failed the test.
Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by minitoar on Saturday May 23, 2020 @01:07PM (#23284575)
If your security model requires people to never open an untrusted link in their browser, you just cannot allow open Internet access
Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by krapht on Saturday May 23, 2020 @02:42PM (#23285329)
Isn't this fairly common? I've now worked at several organizations where sensitive information was stored on air-gapped networks. Software updates or data were moved in and out using pre-approved external drives.

I tend to think this is good software dev practice anyway. You ought to be able to test everything on your testing servers, and if this doesn't adequately reproduce the production environment, it's a problem with your test system.

Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by JoshTriplett on Saturday May 23, 2020 @03:24PM (#23285632)
> I've now worked at several organizations where sensitive information was stored on air-gapped networks.

Then you won't be processing email on machines on those networks.

Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by staticassertion on Saturday May 23, 2020 @02:49PM (#23285384)
No that is not common.
Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by minitoar on Sunday May 24, 2020 @02:10PM (#23293334)
It is common in the sense that it's done frequently enough that we don't need to reinvent it. Most orgs don't want that level of security & inconvenience. FWIW I personally have never encountered it.
Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by bpodgursky on Saturday May 23, 2020 @01:06PM (#23284564)
This is kinda ridiculous. You first need the email client to have a bug which enables some kind of cross-site scripting just rendering an email, then a sandbox bug for a webpage to leak into the underlying system, and THEN a bug for the VM to escape to the parent OS.

At that point, I think it's as likely that your airgapped email laptop can hack into your work machine through local network exploits.

If you think a hacker is going to manage all that, you might as well assume that the hacker can trick gmail in to opening the email for you. There's a point at which we have to realistically assume that some layer of security works, and go about our lives.

Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by Godel_unicode on Saturday May 23, 2020 @03:21PM (#23285609)
> airgapped...local network exploits.

I'm curious what definition of airgap you're using?

Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by libria on Saturday May 23, 2020 @07:03PM (#23287394)
Like other words whose scope has expanded meaning (e.g., serverless, drone), airgap can simply mean segregated network and not just completely unplugged.

AWS uses it this way: https://aws.amazon.com/blogs/publicsector/announcing-the-new...

Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by Godel_unicode on Sunday May 24, 2020 @01:32AM (#23289371)
1. Nothing about that post says it's just network layer segmentation. C2S is it's own region, with multiple AZs (data centers). Why would you believe those are collocated with commercial AWS and not, as they write, air-gapped.

2. Please don't contribute to giving marketing license to remove what little meaning words still have.

Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by Zenbit_UX on Saturday May 23, 2020 @03:28PM (#23285660)
The wrong one I suspect. An Airgapped machine is a term reserved for a pc never connected to the internet, hence the gap. Usually for extreme security concerns like managing a paper crypto wallet or grid infrastructure.
Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by bpodgursky on Saturday May 23, 2020 @05:36PM (#23286721)
Yeah, I should have just said standalone in this case.
Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by stepanhruda on Sunday May 24, 2020 @11:19AM (#23292098)
You are confusing executing untrusted code in a VM with opening something in a browser in a VM - would really need to be a double VM escape.
Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by arpa on Sunday May 24, 2020 @02:05AM (#23289510)
Clearly your threat model adversary is Mossad.
Re:Gitlab phished its own work-from-home staff, and 1 in 5 f... by leppr on Monday May 25, 2020 @06:57AM (#23299871)
It is a paranoid stance. But if you are a developer in a large company, think about how likely it is that your computer has (direct or not) access to data/funds worth more than $100k to someone, and what kind of exploits that money can buy.