Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Endpoint

8/14/2019
11:30 AM
50%
50%

BioStar 2 Leak Exposes 23GB Data, 1M Fingerprints

Thousands of organizations, including banks, governments, and the UK Metropolitan Police, use the biometric security tool to authenticate users.

Researchers with VPNMentor have discovered a massive leak in biometric security platform BioStar 2, which uses facial recognition and fingerprint scanning as part of its means to identify users. Thousands of organizations use the tool to control access to buildings and secure areas.

Suprema, the security firm that built BioStar 2, recently partnered with Nedap to integrate the platform into its AEOS access control system. More than 5,700 institutions across 83 countries, including local businesses, governments, banks, and the UK's Metropolitan Police, use AEOS.

Noam Rotem and Ran Locar, both Internet privacy researchers, first detected the leak on August 5 while scanning ports as part of a Web-mapping project. Their team hunts for familiar IP blocks and uses them to find holes in a company's Web system. When these holes are found, the researchers then look for vulnerabilities that could lead to a data breach. During this process, the team found large chunks of BioStar 2's database unsecured and unencrypted.

The database held "almost every kind of sensitive data available," researchers wrote in a blog post. They could access more than 27.8 million records and a total of 23 GB of data, including more than 1 million fingerprints; facial recognition data and user images; access to client admin panels, dashboards, back-end controls, and permissions; unencrypted usernames and passwords, records of entry and exit to secure areas; and employee records.

"One of the more surprising aspects of this leak was how unsecured the account passwords we accessed were," they point out. "Plenty of accounts had ridiculously simple passwords, like 'Password' and 'abdc1234.'" While some users had more complex passwords, the researchers were able to view passwords across the database because they were stored as plaintext files.

Following a rocky disclosure process, BioStar 2 secured the database on August 13.

Read more details here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-20001
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
CVE-2020-36317
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
CVE-2020-36318
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
CVE-2021-28875
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
CVE-2021-28876
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety r...