Synopsis
Tenable has discovered that default credentials for PostgreSQL are used in Cisco Energy Management.
Default PostgreSQL Credentials
Default credentials are used by Cisco Energy Management to access a local PostgreSQL database. This database stores application data, including user password hashes. In order to exploit this vulnerability, [by default] an attacker must have local access to the host operating system; however, this depends on the configuration of PostgreSQL.
The default credentials for the PostgreSQL database are:
Username: postgres Password: Pemadmin123!
The hard-coded password is checked for several times throughout the codebase. Additionally, the password is stored in jemprocessor.conf as ciphertext; however, this password may be decrypted using the application secret key.
As stated above, by default, an attacker must have local access to exploit this issue. This is due to the configuration of the PostgreSQL server. If a system administrator were to modify the configuration to allow external network connections, a remote access vector would be created.
Solution
Upgrade to Cisco Energy Management version 5.2.3.Additional References
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20181204-ems-sql-passwrdDisclosure Timeline
All information within TRA advisories is provided “as is”, without warranty of any kind, including the implied warranties of merchantability and fitness for a particular purpose, and with no guarantee of completeness, accuracy, or timeliness. Individuals and organizations are responsible for assessing the impact of any actual or potential security vulnerability.
Tenable takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you please work with us to quickly resolve it in order to protect customers. Tenable believes in responding quickly to such reports, maintaining communication with researchers, and providing a solution in short order.
For more details on submitting vulnerability information, please see our Vulnerability Reporting Guidelines page.
If you have questions or corrections about this advisory, please email [email protected]