Patterson Dental Eaglesoft uses a hard-coded database password across installations
Original Release date: 30 Mar 2016 | Last revised: 30 Mar 2016
Patterson Dental Eaglesoft is a dental records software.
Eaglesoft uses a hard-coded database password that is shared across all installations.
CWE-798: Use of Hard-coded Credentials – CVE-2016-2343
According to the researcher, Eaglesoft uses hard-coded credentials to access a database back-end.
The credentials are the same across installations of Eaglesoft.
Sensitive patient information is contained in Eaglesoft databases.
An administrator is unable to change these credentials without breaking access to the back-end database.The researcher has published a blog post with more information.
An attacker with knowledge of the hard-coded credentials and with network access to the database may be able to obtain sensitive patient information.
The CERT/CC is currently unaware of a full solution to this problem.Offices deploying Eaglesoft should consider the following workarounds and mitigations:
Restrict Network AccessAs a general good security practice, only allow connections from trusted hosts and networks. Restricting access would prevent an attacker from using the hard-coded credentials from a blocked network location.Do not allow the Eaglesoft database to be accessed by unauthorized users on an insecure wireless network.
If the Eaglesoft database is accessible from an insecure wireless network, a remote attacker may be able to gain access using the hard-coded credentials. Wireless access points should be configured to use WPA2 encryption and disable the WiFi Protected Setup (WPS) PIN.
Encryption standards such as Wired Equivalent Privacy (WEP) can be easily cracked and should not be relied on to secure wireless networks.
Vendor Information (Learn More)
19 Feb 2016
30 Mar 2016
If you are a vendor and your product is affected, let us know.
CVSS Metrics (Learn More)
Thanks to Justin Shafer for reporting this vulnerability.
This document was written by Garret Wassermann.
CVE IDs: CVE-2016-2343
Date Public: 15 Feb 2016
Date First Published: 30 Mar 2016
Date Last Updated: 30 Mar 2016
Document Revision: 42
If you have feedback, comments, or additional information about this vulnerability, please send us email.