5 ms·
You missed the part where he immediately reported the vulnerability to his manager, security team and execs and got the assurance that it was being handled. If
by paxys 5y ago
You missed the part where he immediately reported the vulnerability to his manager, security team and execs and got the assurance that it was being handled. If after that he is still thrown under the bus and fired, it's clear that someone at his own company dropped the ball and put the blame on him. I wouldn't be surprised if the actual fraud was committed by one of these people as well, using the very hack that he found and disclosed.
- jahewson 5y agoAgreed that anyone who knew about the flaw should be as suspect as the employee in question. But what was this guy doing pentesting a competitor instead of performing his job duties - that’s grounds for being fired right there. Even with an “ok” outcome he’d have arguably caused harm to his employer.
- Brian_K_White 5y agoI know right? I bet he even went to the bathroom and even slept at night. Imagine!
- MathCodeLove 5y agoBecause that's definitely the same thing.
- Brian_K_White 5y ago
- tptacek 5y agoCould you both maybe stop? We get it, you contemptuously disagree with each other.
- paxys 5y agoMaybe, but if his company really had a problem with it he would have been fired or at least repremanded when he initially brought up the problem, not months later.
- SamBam 5y agoEven ignoring that most software jobs understand that a small amount of time just noodling away on tech stuff is to be expected as part of the job, exploring a competitor's public APIs seems very closely aligned with many programmer's priorities.
- ivraatiems 5y agoFinding a vulnerability is one thing. Using it is another. This person overstepped pretty severely and I'm not shocked at all that they got fired. And honestly, writing this post at all continues to show bad judgment. I don't think this person understands where white-hat boundaries are, or how to deal with being accused of a crime. Please reconsider if you think doing something like this to your competitors - or anyone - without some kind of program of consent on their part (like the previously mentioned Project Zero) is a good idea.
- paxys 5y agoHow did he "use" the vulnerability? What did he do that qualified as overstepping? He literally logged into a website and made requests to a hidden endpoint with random IDs. When he realized he was looking at production user info he stopped and reported it to higher ups. The process he has described is right out of the white hat guidebook. What would you have done differently?
- jorgesborges 5y agoHe didn’t exactly stop. He could have quit poking around once alarm bells started ringing but he wanted to see how bad it got so he continued to poke around. Knowing when to stop should probably be a white-hat quality.
- tptacek 5y agoThis happens a lot! It's gotten people in trouble even in situations like bug bounty programs, where some amount of testing is authorized --- there's a delicate set of norms about stopping your exploration when you find a problem. In a situation where there's no prior authorization --- as is likely the case here --- violating whatever implicit norms exist can easily get you in legal trouble. At the very least, if you stumble across something that spits out a plaintext credit card number, stop right there and don't do another damn thing with the target. Don't see which credit card numbers you can see, don't change the `/100` in your URL to `/101`, just stop.
- stjohnswarts 5y agoSave those emails folks... Never take a hand shake or a voice confirmation on something that could get you in trouble.
- tluyben2 5y agoThe problem is that many people still insist on doing things in person or via a ‘quick call’. I have been around long enough that I insist on chat and email; voice is fine for fleshing out features and such but things like this or basically anything that could come back to you, should be in writing with tons of Ccs. I know many people who insist on phone or personal because they are too lazy to read and write, but I definitely also know a % who do it because then there is no verifiable record. And so I err on the side of safety and do everything in writing.
- oblio 5y agoWhat you do in those cases, though they can deny they received the email or read it, is to send a sort of "meeting notes" email to them, where you say something like "as agreed during our phone discussion earlier today...". That way you create a sort of trail that a discussion took place and at least that was your understanding at the time. Even worse if it can be proved that they received the email and read it. Because in that case if they don't reply disagreeing, you can argue that the silence was an approval of your account.
- tluyben2 5y ago> though they can deny they received the email or read it, That’s why I put many Ccs and ask them to respond if they agree or not; I make sure they do. This is always never, at that time, an adversary type of thing, so people generally play ball automatically. When things go rotten then we have everything to win. This happened a few times in court.
- stjohnswarts 5y agoThen "confirm" it over email :) . This almost always works "Per our discussion I'm getting ready to {bullet_list_of_items}" Edit: someone mentioned using CC as well to all those involved in the "plan", that's something I do as well but didn't think about it
- deleted 5y ago[deleted]
- de6u99er 5y agoThat's an important point, which will make white hats think twice if they are going to report stuff like this in the future or keep it to themselves and deny anything that might circle back.
- mkdirp 5y ago> it's clear that someone at his own company dropped the ball and put the blame on him Hard disagree. Why is he reporting it to his own company? It's in his company's best interest for a competitor to have a security issue. He should have gone directly to the competitor's security team. Could have potentially gone anonymous. Could have gone through another person. A reputable security researcher. Lots of other things he could have done, but didn't.
- neves 5y agoSure he could, but his "mistake" was to act in good faith. He reported to his own employer to gain points inside his company. He's showing everybody how smart and competent he is. Maybe he will get a promotion. Moral lesson: your employer isn't your friend. They will throw you under a bus in a blink. Always cover your a*.