Connect with us


FitMetrix user data exposed via passwordless ElasticSearch server cluster



Data for an unknown number of FitMetrix users was left exposed on the Internet via a cluster of ElasticSearch servers, a security researcher has discovered.

The servers, which were not secured with an access password, allowed anyone knowing their IP address to access a trove of information, some of which contained the personal data of FitMetrix users.

According to its website, FitMetrix is a company that provides heart rate monitoring software for gyms, studios, corporate wellness programs, and healthcare professionals. The company was founded in 2013 and acquired earlier this year by Mindbody, Inc., another company that provides a large catalog of cloud-based business management software for the wellness services industry.

The exposed FitMetrix server cluster was discovered by Bob Diachenko, Director of Cyber Risk Research at cyber-security firm Hacken.

Diachenko told ZDNet the exposed ElasticSearch server cluster –a technology used for powering distributed search technologies– contained hundreds of millions of data records.

Not all were customer profiles, and some also contained information about facilities, and other data points, Diachenko told ZDNet, but when user records were exposed, they usually contained the user’s name, gender, birth date, email, username, body size measures, and various FitMetrix program indicators. See the image attached below.

Bob Diachenko

Diachenko told ZDNet he was not able to determine the exact number of user details exposed in the ElasticSearch server cluster, but, in total, the servers appeared to contain over 119GB of data. In an SEC filing, MindBody claimed to serve over 35 million monthly active users, but it is unclear how many of those are using its FitMetrix system.

Additionally, the researcher also says the servers exposed an API key that seemed to be used for managing the FitMetrix server infrastructure.

Last but not least, he also discovered a ransom note that appears to have been written inside the ElasticSearch servers by a remote attacker. This message was as follows:


Ransom notes left inside ElasticSearch servers have been first seen in January 2017, when hackers realized they could place such messages inside exposed servers and trick server owners into paying ransoms. In most reported cases, attackers didn’t delete or encrypt data, but merely hoped to scare a victim into paying the ransom demand.

Nonetheless, the presence of this ransom note means the FitMetrix server was left exposed online enough to be scanned and discovered by at least two persons –Diachenko and the ransomer.

The researcher, who identified the server last week, responsibly disclosed the exposed servers to Mindbody. After several failed attempts of getting in contact with the company, Mindbody secured the servers as soon as they were made aware of the issue yesterday.

“We recently became aware that certain data associated with FitMetrix technology stored online may have been publicly exposed. We took immediate steps to close this vulnerability,” said Jason Loomis, MINDBODY Chief Information Security Officer, in a statement provided to ZDNet via email.

“Current indications are that this data included a subset of the consumers managed by FitMetrix, which was acquired by MINDBODY in February 2018, and did not include any login credentials, passwords, credit card information or personal health information,” he added.

“MINDBODY takes the privacy and security of our customer and consumer data seriously, and we will leverage this incident to continuously improve our security posture.”

Previous and related coverage

Source link

Source link

Continue Reading
Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *


Managing Vulnerabilities in a Cloud Native World



This free 1-hour webinar from GigaOm Research brings together experts in Cloud Native Vulnerability Management, featuring analyst Iben Rodriguez and special guest from Palo Alto Networks, John Morello. The discussion will focus on optimizing cloud security posture and integration with enterprise tool sets.

We will review platforms delivering Security Posture Management and Workload Protection for Microservice based and Hybrid Cloud Workloads.

Registrants will learn how new customers can benefit from Prisma Cloud to better secure their complex multi-cloud environments. Existing customers will learn about new features they can take advantage of and how to optimize their limited resources.

Register now to join GigaOm and Palo Alto Networks for this free expert webinar.

The post Managing Vulnerabilities in a Cloud Native World appeared first on Gigaom.

Continue Reading


Security Tools Help Bring Dev and Security Teams Together



Software development teams are increasingly focused on identifying and mitigating any issues as quickly and completely as possible. This relates not only to software quality but also software security. Different organizations are at different levels when it comes to having their development teams and security teams working in concert, but the simple fact remains that there are far more developers out there than security engineers.

Those factors are leading organizations to consider security tooling and automation to proactively discover and resolve any software security issues throughout the development process. In the recent report, “GigaOm Radar for Developer Security Tools,” Shea Stewart examines a roundup of security tools aimed at software development teams.

Stewart identified three critical criteria to bear in mind when evaluating developer security tools. These include:

  • Vendors providing tools to improve application security can and should also enhance an organization’s overall security posture.
  • The prevailing “shift-left” mindset doesn’t necessarily mean the responsibility for reducing risk should shift to development, but instead focusing on security earlier in the process and continuing to do so throughout the development process will reduce risk and the need for extensive rework.
  • Security throughout the entire software development lifecycle (SDLC) is critical for any organization focused on reducing risk.

Figure 1. How Cybersecurity Applies Across Each Stage of the Software Development Lifecycle *Note: This report focuses only on the Developer Security Tooling area

Individual vendors have made varying levels of progress and innovation toward enhancing developer security. Following several acquisitions, Red Hat, Palo Alto Networks, and Rapid7 have all added tooling for developer security to their platforms. Stewart sees a couple of the smaller vendors like JFrog and Sonatype as continuing to innovate to remain ahead of the market.

Vendors delving into this category and moving deeper into “DevSecOps” all seem to be taking different approaches to their enhanced security tooling. While they are involving security in every aspect of the development process, some tend to be moving more quickly to match the pace of the SDLC. Others are trying to shore up existing platforms by adding functionality through acquisition. Both infrastructure and software developers are now sharing toolsets and processes, so these development security tools must account for the requirements of both groups.

While none of the 12 vendors evaluated in this report can provide comprehensive security throughout the entire SDLC, they all have their particular strengths and areas of focus. It is therefore incumbent upon the organization to fully and accurately assess its SDLC, involve the development and security teams, and match the unique requirements with the functionality provided by these tools. Even if it involves using more than one at different points throughout the process, focus on striking a balance between stringent security and simplifying the development process.

Read more: Key Criteria for Evaluating Developer Security Tools, and the Gigaom Radar for Developer Security Tool Companies.

The post Security Tools Help Bring Dev and Security Teams Together appeared first on Gigaom.

Continue Reading


Key Criteria for Evaluating User and Entity Behavior Analytics (UEBA)



Cybersecurity is a multidisciplinary practice that not only grows in complexity annually but evolves nearly as quickly. A survey of the security landscape today would reveal concerns ranging from the classic compromised servers to the relatively new DevSecOps practices aimed at securing the rapid deployment of new code and infrastructure. However, some things remain constant no matter how much change is introduced. While technology evolves and complexity varies, there is almost always a human component in
risks presented to an organization.

User Behavior Analysis (UBA) was designed to analyze the actions of users in an organization and attempt to identify normal and abnormal behaviors. From this analysis, malicious or risky behaviors can be detected. UBA solutions identify events that are not detectable using other methods because, unlike classic security tools (an IDS or SIEM for example), UBA does not simply pattern match or apply rule sets to data to identify security events. Instead, it looks for any and all deviations from baseline user activity.

As technology advanced and evolved, and the scope of what is connected to the network grew, the need to analyze entities other than users emerged. In response, entity analysis has been added to UBA to create UEBA or User and Entity Behavior Analysis. The strategy remains the same, but the scope of analysis has expanded to include entities involving things like daemons, processes, infrastructure, and so on.

How to Read this Report

This GigaOm report is one of a series of documents that helps IT organizations assess competing solutions in the context of well-defined features and criteria. For a fuller understanding consider reviewing the following reports:

Key Criteria report: A detailed market sector analysis that assesses the impact that key product features and criteria have on top-line solution characteristics—such as scalability, performance, and TCO—that drive purchase decisions.

GigaOm Radar report: A forward-looking analysis that plots the relative value and progression of vendor solutions along multiple axes based on strategy and execution. The Radar report includes a breakdown of each vendor’s offering in the sector.

Solution Profile: An in-depth vendor analysis that builds on the framework developed in the Key Criteria and Radar reports to assess a company’s engagement within a technology sector. This analysis includes forward-looking guidance around both strategy and product.

The post Key Criteria for Evaluating User and Entity Behavior Analytics (UEBA) appeared first on Gigaom.

Continue Reading