UUUM: an administrator authentication key for GitHub was readable on a web server, leaving all source code and personal data obtainable
An administrator key for GitHub was readable on a web server from June 19 to October 21. The source code was accessed, but no access to personal data was found.
Disclosed
2022-11-10
Organizations involved
1
Leaked or at risk
Unknown
Downtime
Unknown
What happened
From this day, the authentication key that could fetch the source code of the whole group was readable on the web server. [1]
It confirmed that the key was readable and disabled it that day. It then also changed the access keys of the databases. [1]
It reported to the Personal Information Protection Commission. [1]
Impact
With the key anyone could fetch all of the group's source code on GitHub, including private repositories, and the access keys in the code allowed viewing the personal data in the databases. The GitHub logs show access to the source code of external systems (CREAS, UUUM iD) and internal systems. No history of database access was found and no misuse of personal data. The cause was uploading a key with strong privileges to a production server. [1]
Timeline
- Started 2022-06-19
- Detected 2022-10-21
- Disclosed 2022-11-10
- 144 days
Attack or cause
- Method
- [Misconfiguration]
- Impact
- [Data leak]
- Entry point
- Unknown
Data exposed or at risk
–
Organizations involved
[Breached][Major]Tokyo, MinatoPersonal services and entertainment
UUUM Inc.
Sources
- [1][Official]個人情報流出の可能性に関するお詫びとお知らせ | UUUM株式会社(ウーム株式会社)UUUM Inc. · 2022-11-10
- [2][News]UUUMがGitHub上で情報漏えいの可能性 認証キーをWebサーバに放置 - ITmedia NEWSITmedia NEWS · 2022-11-10