Rakuten Group: a setting error in an outside sales management cloud left up to about 1.49 million records open for nearly five years, and access from overseas was confirmed
A setting error in an outside cloud used by Rakuten, Rakuten Card and Rakuten Edy left data open from January 2016, and overseas access was confirmed.
Disclosed
2020-12-25
Organizations involved
3
Leaked or at risk
1.5M
1,487,771
Downtime
Unknown
What happened
From this day, a setting error in the outside cloud sales management system used by the group let outside parties reach the data. [1] [4]
An outside security expert pointed out that the data was open to outsiders. The group's security unit began responding the same day. [1] [4]
The settings were corrected. No outside access has been seen since. [1]
Impact
Company and data | Records open | Access confirmed |
|---|---|---|
Rakuten: corporate inquirers and shop data for Rakuten Ichiba (company and shop names, addresses, representative and contact names, phone, fax, mail addresses, sales records) | up to 1,381,735 | 208 |
Rakuten Card: business loan applicants (business names and accounts, representatives' names, addresses, birth dates, driver licence numbers and personal accounts, guarantors, loan requests) | up to 16,895 | 304 |
Rakuten Edy: applicants for the balance transfer service for broken devices (name, phone number of the broken device, Edy number) | up to 89,141 | 102 |
Rakuten Card's count rose from 15,415 to 16,895 in an update on January 26, 2021. The exposure ran from January 15, 2016 until November 24 for Rakuten and until November 26 for Edy and Rakuten Card. Rakuten Card member data sits in a separate system and was not affected. [1] [3]
Third parties accessed some of the data from overseas. No misuse or harm has been confirmed. The group reported to the Personal Information Protection Commission and the supervising ministries and is notifying the companies and individuals who may have been affected. The cause was an inadequate security setting in the use of the outside system, and the group is asking its provider for details. [1]
Timeline
- Started 2016-01-15
- Detected 2020-11-24
- Disclosed 2020-12-25
- 1806 days
Attack or cause
- Method
- [Misconfiguration]
- Impact
- [Data leak]
- Entry point
- Unknown
Data exposed or at risk
Organizations involved
[Breached][Critical]Tokyo, MinatoFinance and insurance16,895 leaked
Rakuten Card Co., Ltd.[Breached][Major]Tokyo, MinatoFinance and insurance89,141 leaked
Rakuten Edy, Inc.[Breached][Major]Tokyo, SetagayaInformation and communications1,381,735 leaked
Rakuten Group, Inc.The company was then named Rakuten, Inc.
Sources
- [1][Official]クラウド型営業管理システムへの社外の第三者によるアクセスについてRakuten Group · 2020-12-25
- [2][News]楽天、クラウド設定にミス 5年間、外部閲覧可能に 148万件流出Nikkei · 2020-12-27
- [3][News]楽天グループのクラウド型営業管理システムに設定不備、社外からアクセス可能にScanNetSecurity · 2020-12-28 08:00
- [4][News]クラウド設定ミスで顧客情報が流出 - 楽天グループ3社Security NEXT · 2020-12-28