A database of over 350 million customer records exposed from unsecured Elasticsearch cluster belonging to voice over-internet-protocol company Broadvoice.
The database was uncovered by security researcher Bob Diachenko, on October 1. He observed that the unprotected Elasticsearch cluster contained several information found unprotected.
What are the Data Exposed
An amount of 350 million customer records exposed through that includes caller names, phone numbers, locations.
One of the databases found to contain hundreds of thousands of voicemails, other sensitive information such as medical prescriptions and financial loans.
The database was discovered by Diachenko on October 1, 2020, and the same it was disclosed to Broadvoice and it has been secured by October 4th.
Following are the full list of data exposed
- Full caller name
- Caller identification number
- Phone number
- date of birth
- Caller name (full name, business name, or a generic name such as “wireless caller”)
- Caller phone number
- A name or identifier for the voice mailbox (for example, a first name or general label, such as “clinical staff” or “appointments”)
- Internal identifiers
When the data exposed to the public, there be a choice for unauthorized parties access, if attackers access the data they use them to launch targeted attacks.
Broadvoice said that ” we take data privacy and security seriously. We learned that on October 1st, a security researcher was able to access a subset of b-hive data. The data had been stored in an inadvertently unsecured storage service Sept. 28th and was secured Oct. 2nd”.
Broadvoice is a privately owned company that provides services like telephone services, UCaaS, SIP Trunking, Network, and Security, along with Virtual Call Center solutions to enable business customers to transmit/ receive voice and video communications via a broadband Internet connection or cellular phone.
Regardless of the size of the organization, anyone who uses cloud technology is subject to the risk of unintentional exposure.
Amazon published an article on how to secure the files in my Amazon S3 bucket details the access restrictions.
To read the original article: