
Potential Risks of Open Ports and Infrastructure Exposure
An open port is a network endpoint on a host that could potentially accept connections for a range of services. According to an IoT search engine review of the IP address, in this case, there were a total of 89 open ports. While not all open ports are dangerous, any internet-facing host with this many open ports could potentially create a large attack surface for cybercriminals to target. Common ports that are usually associated with remote admin, directory/DB, VPN, messaging, and security tooling should not be publicly accessible. Open ports could hypothetically allow criminals to test the network to try and identify known-vulnerability exploits and misconfigurations; they could also attempt brute-force or credential-stuffing, service fingerprinting, and even DDoS attacks on internal non-public infrastructure. Some of the records I saw appeared to indicate internal services and access data that was marked as “production”. They referenced databases and backend update servers. The potential risk of any organization exposing critical infrastructure details is that they could be used as a roadmap or a blueprint for how the service operates. The exposure of server names, IP addresses, and even potential usernames could provide sensitive details about the organization’s internal systems. Even without credentials or passwords, the exposure of operational details could increase the potential for unauthorized access to production databases and any information they contain. Exposing detailed internal and infrastructure data could hypothetically make it easier for criminals to attempt to compromise the system. Ransomware is a serious concern for any organization and, unfortunately, most modern ransomware variants can easily locate, encrypt, or delete backups with the goal of forcing the victim to pay a ransom. My advice to anyone who believes that their email may have been leaked in a data breach is to know the most common threats. As a general rule, don’t click links or open attachments in unexpected messages from unknown senders. Always verify senders and only communicate through official channels if the communications contain sensitive information. This can limit the chances of a targeted phishing or social engineering attempt using real information from a breach or hacked data. If you receive unexpected MFA requests or failed login attempts, it is a good idea to change the password on the affected account to a strong unique password. Use an authenticator app or hardware key when possible and make sure you know what apps or accounts are connected to your email. It is also a good idea to review account recovery information (such as phone numbers or backup emails) and make sure they are up to date. Some email providers offer features that send alerts and notifications of account changes or failed login attempts. Keeping account data accurate and configuring alert settings can help prevent account takeover attempts or help recover the account if it is compromised.Disclosure
As an ethical security researcher, I do not download or extract data. I often manually review and query a limited amount of data to understand what was there, who it affects, its geoscope, and potential risks. According to Netcore Cloud’s website, their client base includes many companies and brands that are well-known and have extensive numbers of customers. It is not known how many of the approximately 6,500 businesses that use Netcore may have been affected (or whether any were affected at all) by the reported exposure. While this database is one of the largest I have discovered in many years, the 40 billion records it holds are most likely not all unique. Account notifications, mailing lists, and general outreach would likely generate recurring messages to the same email address, so the number of total records is larger than the total number of potentially affected individuals. Nevertheless, the reality of this exposure is that this information could potentially provide cybercriminals with key trends and insights into account activities and the contact information of many millions of individuals. I imply no wrongdoing by Netcore Cloud, or its employees, agents, contractors, affiliates, and/or related entities. I do not claim that any internal, employee, customer, or user data was ever at imminent risk. The hypothetical data-risk scenarios I have presented in this report are strictly and exclusively for educational purposes and do not reflect, suggest, or imply any actual compromise of data integrity. It should not be construed as a reflection of or commentary on any particular organization’s specific practices, systems, or security measures. I do not engage in any activities beyond identifying the security vulnerability and, where possible, notifying the relevant parties involved. I disclaim any and all liability from the use, interpretation, or reliance on this disclosure. I publish my findings to raise awareness of issues of data security and privacy. My aim is to encourage organizations to proactively implement measures to safeguard sensitive information against unauthorized access.Website Planet’s Recent Publications
At Website Planet we work with an experienced team of ethical security research experts who uncover and disclose serious data leaks. Recently, cybersecurity expert Jeremiah Fowler discovered and disclosed a non-password protected database containing 85,361 files totaling 158 GB of data apparently belonging to Rainwalk.He also found another unsecured database containing 178,519 files apparently belonging to Invoicely.