Lucene search
K

MEDHOST Document Management System Hardcoded Credentials

🗓️ 27 Jul 2017 00:00:00Reported by Allen FranksType 
packetstorm
 packetstorm
🔗 packetstormsecurity.com👁 41 Views

MEDHOST Document Management System Hardcoded Credentials vulnerability in hard-coded credentials for PostgreSQL and Apache Solr

Related
Code
ReporterTitlePublishedViews
Family
CNVD
MEDHOST Perioperative Information Management System Unauthorized Operation Vulnerability
27 May 201600:00
cnvd
CNVD
MEDHOST Document Management Information Disclosure Vulnerability (CNVD-2017-27413)
1 Aug 201700:00
cnvd
CNVD
MEDHOST Document Management Information Disclosure Vulnerability
1 Aug 201700:00
cnvd
CNVD
MEDHOST Document Management Hardcoded Certificate Disclosure Vulnerability
1 Aug 201700:00
cnvd
CVE
CVE-2016-4328
10 Jun 201601:00
cve
CVE
CVE-2017-11614
25 Jul 201717:00
cve
CVE
CVE-2017-11693
28 Jul 201713:00
cve
CVE
CVE-2017-11694
28 Jul 201713:00
cve
Cvelist
CVE-2016-4328
10 Jun 201601:00
cvelist
Cvelist
CVE-2017-11614
25 Jul 201717:00
cvelist
Rows per page
`MEDHOST Document Management System contains multiple hard-coded credentials  
  
CVE-2017-11693 & CVE-2017-11694  
  
Overview  
------------  
Medhost Document Management system for all versions contains hard-coded credentials  
used for customer database and Apache Solr access. This is a new vulnerability  
not related to CVE-2016-4328 or CVE-2017-11614.  
  
Description  
------------  
  
MEDHOST Document Management System contains multiple hard-coded credentials that are  
used for customer database and Apache Solr access. An attacker with knowledge of the  
hard-coded credentials and the ability to communicate directly with the database and  
Apache Solr may be able to obtain or modify sensitive patient and financial  
information. PostgreSQL is used as the Document Management System database. The account name  
is dms. The Apache Solr account name is also dms. These passwords are hard-coded throughout  
the application, and are the same across all installations. Customers do not have the option  
to change passwords. The dms account for PostgreSQL has access to the database schema for  
Document Management System. The dms account for Apache Solr has access to all indexed  
patient documents. PostgreSQL listens on the default TCP port 5432. Apache Solr listens  
on the default TCP port 8080.  
  
WEB-INF/classes/database.properties:  
  
# DMS database settings  
jdbc.driverClass=org.postgresql.Driver  
jdbc.url=jdbc:postgresql://localhost:5432/dms  
jdbc.username=dms  
jdbc.password=[redacted]  
  
# Liquibase flag  
run.liquibase.on.startup = true  
  
WEB-INF/classes/solr.properties:  
  
solr.url=http://localhost:8080/solr/dms  
solr.username=dms  
solr.password=[redacted]  
  
Impact  
------------  
  
An attacker with knowledge of the hard-coded credentials and the ability to communicate  
directly with the application database server may be able to obtain or modify patient and  
financial information.  
  
Solution  
------------  
  
The vendor has not issued a patch and has been unresponsive to this information after 3  
attempts to communicate.  
  
Restrict network access  
  
As a general security practice, only allow connections from trusted hosts and networks.  
Restricting access would prevent an attacker from using the hard-coded database credentials  
from a blocked network location.  
`

Data

Build on a solid foundation with Vulners data

We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data

Api

Power your application with Vulners API

The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access

App

Assess and manage vulnerabilities with Vulners tools

Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation