美国当地时间周五晚上，有开发者表示收到来自 Docker 的官方邮件，邮件内容显示由于 Docker Hub 遭受非法入侵，已导致 19 万个帐号的敏感数据被泄露，这些数据包括小部分用户的用户名和哈希密码，以及用于自动构建 Docker 镜像而授权给 Docker Hub 的 GitHub 和 Bitbucket token。
Docker Hub 是 Docker 容器镜像的官方存储库，提供给 Docker 开发者用于上传/下载容器镜像。
![]()
![]()
Docker 方面表示，发现漏洞后已立即采取干预措施来保护数据，并尽力降低对用户造成的影响。
按照 Docker 的官方说法，在黑客入侵 Docker Hub 后的短时间内就发现了问题，不过仍有 19 万个帐号的数据已遭泄露，大约是总用户数的 5%。
Docker 发现问题后立即向用户告知了这一消息，并通知用户重置密码（包括使用其他使用相同用户名和密码的平台）。
此外，对于使用了自动构建服务并可能受影响的用户，Docker 已撤销他们的 GitHub token 和访问密钥，并提醒他们重新连接到存储库，然后检查安全和登录日志以查看是否发生了任何异常操作，例如是否存在通过未知的 IP 地址进行任何未经授权的访问。
虽然受影响的用户只有 5%，看起来问题不是十分严重，但事实并非如此。要知道绝大多数 Docker Hub 用户都是大公司的内部员工，他们的帐号可能正在使用自动构建容器服务，然后在实际生产环境中部署这些容器。
如果他们没有及时重置帐号密码，那么其帐号的自动构建服务会存在极大的安全风险 —— 被攻击者植入恶意软件。
Docker 表示目前仍在调查此事件，调查清楚后会分享详细信息。不过这起安全事件尚未在公司网站上披露，仅通过电子邮件通知用户。邮件内容如下：
On Thursday, April 25th, 2019, we discovered unauthorized access to a single Hub database storing a subset of non-financial user data. Upon discovery, we acted quickly to intervene and secure the site.
We want to update you on what we've learned from our ongoing investigation, including which Hub accounts are impacted, and what actions users should take.
Here is what we’ve learned:
During a brief period of unauthorized access to a Docker Hub database, sensitive data from approximately 190,000 accounts may have been exposed (less than 5% of Hub users). Data includes usernames and hashed passwords for a small percentage of these users, as well as Github and Bitbucket tokens for Docker autobuilds.
Actions to Take:
- We are asking users to change their password on Docker Hub and any other accounts that shared this password.
- For users with autobuilds that may have been impacted, we have revoked GitHub tokens and access keys, and ask that you reconnect to your repositories and check security logs to see if any unexpected actions have taken place.
- You may view security actions on your GitHub or BitBucket accounts to see if any unexpected access has occurred over the past 24 hours -see https://help.github.com/en/articles/reviewing-your-security-log and https://bitbucket.org/blog/new-audit-logs-give-you-the-who-what-when-and-where
- This may affect your ongoing builds from our Automated build service. You may need to unlink and then relink your Github and Bitbucket source provider as described in https://docs.docker.com/docker-hub/builds/link-source/
We are enhancing our overall security processes and reviewing our policies. Additional monitoring tools are now in place.
Our investigation is still ongoing, and we will share more information as it becomes available.
Thank you,
Kent Lamb Director of Docker Support info@docker.com
