June 23, 2023 By Jonathan Reed 4 min read

In March 2023, data on more than 56,000 people — including Social Security numbers and other personal information — was stolen in the D.C. Health Benefit Exchange Authority breach. The online health insurance marketplace hack exposed the personal details of Congress members, their families, staff and tens of thousands of other Washington-area residents.

It appears the D.C. breach was due to “human error”, according to a recent report. Apparently, a computer server was misconfigured to allow access to data without proper authentication. Implementing authentication would have been something easy to accomplish. Instead, a door was left wide open for attackers to gain access.

Poorly configured web servers are all too common. In fact, a recent study from a firm that indexes internet-facing devices reported that over 8,000 servers hosting sensitive information are not properly configured.

Easy to identify data exposure

A recent Censys report stated that “data exposures via misconfiguration remain a serious problem. We found over 8,000 servers on the internet hosting potentially sensitive information, including possible credentials, database backups and configuration files.” As per the report, these vulnerabilities were easy to identify, as they would be for even inexperienced threat actors.

Meanwhile, print management software developer PaperCut recently warned customers to update their software immediately. PaperCut makes printing management software utilized by companies, state entities and education. As per their website, PaperCut serves hundreds of millions of people from around the globe.

In a recent vulnerability bulletin, PaperCut said, “We have evidence to suggest that unpatched servers are being exploited in the wild.” Other reports of poorly managed Linux servers and poorly secured Interned-exposed Microsoft SQL (MS-SQL) servers have led to malware entry.

Other findings in the Censys report include:

  • Over 1,000 hosts with over 2,000 SQL database files were exposed with no authentication requirements on the HTTP services themselves
  • More than 18,000 CSV files were publicly exposed on just 147 hosts
  • Over 5,000 hosts had over 5,000 exposed files and directories, indicating they are related to a backup.

Based on its findings, Censys states that vulnerable hosts aren’t only servers with outdated and exploitable software. Vulnerabilities can arise from various sources, including errors in judgment, misconfigurations and rushed work. The firm says a quick and easy solution today may prevent a severe data breach tomorrow.

“The often unglamorous work of asset, vulnerability and patch management is critical for helping reduce an organization’s attack surface. The security issues we’ve explored in this report aren’t a result of zero days or other advanced exploits, but rather misconfiguration and exposure issues that are likely a result of simple mistakes or configuration errors,” Censys noted.

Fixing servers that lack authentication

If a computer server was misconfigured to allow access to data without proper authentication, the following steps can be taken to fix server issues:

  1. Shut down the server: The first step is to immediately shut down the server to prevent or halt unauthorized access to the data.
  2. Investigate the scope of the issue: Once the server is shut down, evaluate the extent of the problem by examining log files, system configuration files and other relevant data to determine the extent of unauthorized access, if any.
  3. Identify the root cause of the problem: Examine the server configuration files, software settings and security policies. Determine whether the misconfiguration was due to a human error, software flaw or something else.
  4. Correct the misconfiguration: Once the root cause has been identified, correct the misconfiguration by updating the server configuration files, software settings or security policies. This may involve reconfiguring access controls, updating software or installing security patches.
  5. Test the fix: After correcting the misconfiguration, test the fix by attempting to access the data without proper authentication. Verify that the fix has been successful and that the data is now secure.
  6. Monitor the server: After the fix has been implemented and tested, monitor the server to ensure that it is functioning properly and that no further security issues arise.
  7. Review security policies and procedures: Lastly, review security policies and procedures to ensure they are adequate to prevent similar security issues in the future. You may need to provide additional training to employees, review access controls or implement new security technologies.

How to secure your server

Securing web servers is required to reduce the risk of unauthorized access and data breaches. Here are some steps you can take to enhance the security of your web server:

  1. Keep server software up to date: Make sure to install the latest security patches and updates for your web server software, as well as any related software components (such as databases and scripting languages).
  2. Use strong authentication: Require strong passwords and two-factor authentication for all user accounts. Use SSH keys instead of passwords for remote access.
  3. Limit access: Limit access to the server to only those who need it. Use firewalls and other access control mechanisms to block unauthorized access.
  4. Secure file and directory permissions: Make sure that sensitive files and directories are only accessible to authorized users. Set file permissions to “read-only” for non-essential files and directories.
  5. Use encryption: Use SSL/TLS encryption for all communication between clients and the server, and encrypt sensitive data stored on the server.
  6. Monitor server logs: Regularly monitor server logs to detect suspicious activity. Use intrusion detection systems (IDS) and other security tools to identify and respond to potential threats.
  7. Back up regularly: Regularly back up your server’s data and configuration files and store backups in a secure location.
  8. Implement security policies: Establish and enforce security policies and procedures for your organization. Educate employees and users about best practices for web server security.

Don’t leave the door open

There certainly are a number of highly sophisticated cyber intruders out there. But many data breaches are the result of simply leaving the front door unlocked. Due to human error, mistakes can lead to the exposure of large amounts of data on a server. The problem is the lack of simple security measures, such as authentication, authorization or filtering. But this is good news since obtainable fixes can improve server security substantially.

More from Network

New cybersecurity sheets from CISA and NSA: An overview

4 min read - The Cybersecurity and Infrastructure Security Agency (CISA) and National Security Agency (NSA) have recently released new CSI (Cybersecurity Information) sheets aimed at providing information and guidelines to organizations on how to effectively secure their cloud environments.This new release includes a total of five CSI sheets, covering various aspects of cloud security such as threat mitigation, identity and access management, network security and more. Here's our overview of the new CSI sheets, what they address and the key takeaways from each.Implementing…

Databases beware: Abusing Microsoft SQL Server with SQLRecon

20 min read - Over the course of my career, I’ve had the privileged opportunity to peek behind the veil of some of the largest organizations in the world. In my experience, most industry verticals rely on enterprise Windows networks. In fact, I can count on one hand the number of times I have seen a decentralized zero-trust network, enterprise Linux, macOS network, or Active Directory alternative (FreeIPA). As I navigate my way through these large and often complex enterprise networks, it is common…

X-Force identifies vulnerability in IoT platform

4 min read - The last decade has seen an explosion of IoT devices across a multitude of industries. With that rise has come the need for centralized systems to perform data collection and device management, commonly called IoT Platforms. One such platform, ThingsBoard, was the recent subject of research by IBM Security X-Force. While there has been a lot of discussion around the security of IoT devices themselves, there is far less conversation around the security of the platforms these devices connect with.…

Topic updates

Get email updates and stay ahead of the latest threats to the security landscape, thought leadership and research.
Subscribe today