Well, this is pretty disappointing. Docker doesn’t let you install it without an account, so I registered and used it for maybe a day in all. And poof, there goes my account data. I’m just hoping that I was using a password manager by then. Any word as to the cause of this? Was something important stored in plaintext, etc.?
> Well, this is pretty disappointing. Docker doesn’t let you install it without an account, so I registered and used it for maybe a day in all. And poof, there goes my account data. Eh? Doesn’t let you use what without an account? Anyone can pull images anonymously. An account is only for publishing.
Docker Hub Hacked – 190k accounts, GitHub tokens revoked, builds disabled
21–30 of 269 posts
Re: Docker Hub Hacked – 190k accounts, GitHub tokens revoked, builds disabled
#22If you got an email you should: - Change your password on https://hub.docker.com - Check https://github.com/settings/security - Reconnect oauth for Automated Builds - Roll over effected passwords and API keys stored in private repos / containers Quick take: - Password hashes - Github tokens - Bitbucket tokens - Your Automated Builds might need new tokens Checking my github logs - It looks like they've known about thi…
Re: Docker Hub Hacked – 190k accounts, GitHub tokens revoked, builds disabled
#23Well, this is pretty disappointing. Docker doesn’t let you install it without an account, so I registered and used it for maybe a day in all. And poof, there goes my account data. I’m just hoping that I was using a password manager by then. Any word as to the cause of this? Was something important stored in plaintext, etc.?
> Well, this is pretty disappointing. Docker doesn’t let you install it without an account, so I registered and used it for maybe a day in all. And poof, there goes my account data. Eh? Doesn’t let you use what without an account? Anyone can pull images anonymously. An account is only for publishing.
Re: Docker Hub Hacked – 190k accounts, GitHub tokens revoked, builds disabled
#24Re: Docker Hub Hacked – 190k accounts, GitHub tokens revoked, builds disabled
#25Re: Docker Hub Hacked – 190k accounts, GitHub tokens revoked, builds disabled
#26Well, this is pretty disappointing. Docker doesn’t let you install it without an account, so I registered and used it for maybe a day in all. And poof, there goes my account data. I’m just hoping that I was using a password manager by then. Any word as to the cause of this? Was something important stored in plaintext, etc.?
Re: Docker Hub Hacked – 190k accounts, GitHub tokens revoked, builds disabled
#27If they had write access, then leaked personal data is the least of anyone's worries. The real concern is how close the hackers came to infiltrating the image source for virtually every modern microservices system. If you could put a malicious image in say alpine:latest for even a minute, there's no telling how many compromised images would have been built using the base in that time.
Re: Docker Hub Hacked – 190k accounts, GitHub tokens revoked, builds disabled
#28Docker Hub being hacked was basically just a question of time. With how much of the internet blindly pulls images from it, the potential gain from hijacking just one high-profile one would be monumental.
But no, not Docker.
You're totally right; with as important as their registry is to well funded attackers, and as startup-y and "agile" as they are, and as godawful as the security practices are that underlie their tools and standards... they hadn't a chance. They still don't.
There is no reason to expect them to get better.
Re: Docker Hub Hacked – 190k accounts, GitHub tokens revoked, builds disabled
#29Docker Hub being hacked was basically just a question of time. With how much of the internet blindly pulls images from it, the potential gain from hijacking just one high-profile one would be monumental.
Re: Docker Hub Hacked – 190k accounts, GitHub tokens revoked, builds disabled
#30Docker Hub being hacked was basically just a question of time. With how much of the internet blindly pulls images from it, the potential gain from hijacking just one high-profile one would be monumental.
As I understand it, there's no element of signing from the actual devs of an image, just from the central trust service of Docker Hub.