Earlier quoted context omitted.
Anyone who tells you they're "encrypting" email addresses in their SaaS app is almost certainly describing a cosmetic security feature. Every day of the week and four times and Tuesday I'd prefer the team that spends their marginal dollar on finding the next marginal reflected XSS bug than the one that wastes it on "two-way encryption of email addresses". I don't know what Weebly does for appsec (I've never worked wi…
In terms of appsec, we run quarterly black box pen tests and annual comprehensive white box pen tests with well regarded firms, and have been rotating vendors on a regular basis for diversity. We also do a lot of stuff internally, like regular scanning, and internal sprints focused on vuln detection. We've been doing this for years. That's not to say we're perfect (we clearly are not) but we do take it seriously.
Weebly hacked, 43M credentials stolen
91–99 of 99 posts
Re: Weebly hacked, 43M credentials stolen
#92Earlier quoted context omitted.
It wasn't swift that was hacked.
Can you elaborate?
What was hacked was the bank where the messages were sent from.
https://www.bloomberg.com/news/articles/2016-05-26/swift-hac...
If you read the article (any of the articles) the headlines always talk about the 'swift hack' however it was the _banks_ that were hacked (and the article says so), not swift.
Re: Weebly hacked, 43M credentials stolen
#93Earlier quoted context omitted.
I believe he meant the will try the top 100 most common passwords on each account on the website directly, resulting on "82% of users at risk", assuming 82% of users use one of these 100 passwords. Strong brute-force protection (eg block account for exponential times) could mitigate this attack vector.
Why are you guys talking about live site and rainbow table??? The attackers have the salts and the hashes, they can brute force the hashes offline with [ocl]hashcat as they wish. Top 100 passwords * 43M accounts is only ~4B hashes to compute. We don't know what bcrypt parameters they used but we're probably talking a few hours here, maybe only a few minutes.
you are right that it's now very easy to use dictionary attacks now, on all the credentials offline. and those with super weak passwords will have their accounts compromised.
Re: Weebly hacked, 43M credentials stolen
#94Earlier quoted context omitted.
I am not trying to start a flame war, just curious why the 2 jokes about Russian hackers being the origin of breaches are being heavily downvoted. I would assume people think they aren't clever or funny, but hopefully not because they disagree that Russia seems to be the catch-all scapegoat right now.
It doesn't matter if people think they're clever or funny, a core tenet of HN is that you downvote cute jokes so that they don't eat all the real discussion like they do on Reddit.
Re: Weebly hacked, 43M credentials stolen
#952nd thing is 2FA. I hope 2FA becomes the standard for all login. Even SMS. ( I know SMS is not save in US, but I am not sure if similar can be said in EU or Japan )
Re: Weebly hacked, 43M credentials stolen
#96Earlier quoted context omitted.
It doesn't matter if people think they're clever or funny, a core tenet of HN is that you downvote cute jokes so that they don't eat all the real discussion like they do on Reddit.
It is a semi-noob illusion that satire and irony-- which underscore & catalyse discussion about relevant and important issues; should be reserved for Reddit. Often, satire is used when it may be difficult to confront an issue directly/the issue itself (or discussion) could be unpopular.
Re: Weebly hacked, 43M credentials stolen
#97Re: Weebly hacked, 43M credentials stolen
#98Earlier quoted context omitted.
What is that going to do, the outcome is the attacker still has the password hash and the linked email address?
So how do they log in without a username & password ?
Re: Weebly hacked, 43M credentials stolen
#99Earlier quoted context omitted.
This is silly – the entire process of "Oh, we got hacked. What did they access? Who's been compromised? Better write an email. Better find a channel to send that email, and wait for it to be sent" could very, very obviously take a couple of days. You are unfairly trivialising that.
My point was transactional emails does not hit any spam filters. And since email services tracks how many of emails were opened, i am pretty sure 'we have been hacked' will be opened quite often and will never be in spam folder.