Cheers theymos! The fact that there were attempts on the server is quite something. Makes you think that with such a exploit that Bitcointalk was still on someones list to try it on, rather than others which were also affected and probably a lot more incentive. Just glad none of them were successful!
This could've easily turned into a 2015 situation or even worse.
so the forum wasn't shut down until around 14:30 UTC, 30 minutes after the public announcement of the vulnerability details, and about 7 hours after some details had begun to leak.
I consider this pretty quick, considering you also have a life outside of this forum!
The funny thing is, when I first visited the forum, all I saw was the default 503 Service Temporarily Unavailable error.
I was literally about to message @Cyrus on Discord and suggest putting up a custom maintenance page with some explanation.
I think this might be the first maintenance / error message I've seen with the forum going down. I think previously it was on Twitter years ago, but yeah this was nice to see considering the circumstances.
Does that apply to accounts that just woke up after over four years?
AFAIK, if you logged in after the hotfix, then probably OK. My understanding, which might be wrong is; malicious actors could've perform 'remote code execution', which they could've gained access to the database. During this time they could've:
- Stolen password hashes / salts
- gathered information when entered into login fields. (so this technically would only expose those that logged in during the time of a compromise).
- Could've put a backdoor into the server which would send out sensitive info (which would expose those that log in even after the hotfix)
- Someone could theoretically have used this months / years ago, but obviously that's incredibly unlikely. Usually, zero day exploits are just that first day exploits that hackers use to quickly compromise their target within a short period of time.
However, it seems theymos has already cleared this and fairly confident none of this happened. Although, it goes without saying 'probably ok' probably isn't good enough. I'd just recommend everyone changes it so er on the side of caution.
I saw other forums and websites were also affected
Yeah, world wide. Basically every website running PHP which is the majority. Banks, news are just some that are affected. Some are still down, as their websites are more complex / larger.
This was the biggest down time ever on the history of the forum if I am not mistakenly. Anyone out there can correct me if I am wrong.
That would probably be 2015. Though, that was also hacked and had all sorts going on without it being down too. Plus, I wasn't around for some of the other compromises the forums suffering like 2011.
True. So, periodic change of password doesn't really help with anything, does it? (provided you have chosen a strong password to begin with which brute force attacks are unlikely to breach).
A lot of organizations suggest changing your password periodically, some as often as two weeks. However, I believe the attitude is changing towards this and we are not in favour of a strong password, and not changing so often. After all, changing regularly includes user based errors which can lead to locking out of their account etc. At the end of the day, the idea is by changing regularly, if the malicious user has access to the hashed version they might be working on solving it, but by changing it regularly you make that moot.
Thus, it leads me to conclude that you are not required to present your present password at all. Just follow the link and set a new one! It would be stupid to require old password anyhow
That's if you reset your password via the "I forgot my password" if you do it within settings, you'll need to enter your current password, this is because you're logged in and any actor who gets access to your computer could potentially try changing the password, so while logged in a password is required if doing it from settings.
However, if your password is of sufficient complexity solving the hash isn't realistic anyway.