Vulnerability Note VU#630239
Epiphany Cardio Server is vulnerable to SQL and LDAP injection
Original Release date: 01 Dec 2015 | Last revised: 09 Dec 2015
The Epiphany Cardio Server is vulnerable to SQL injection and LDAP injection, allowing an unauthenticated attacker to gain administrator rights.
Epiphany Cardio Server was reported as being vulnerable to the following issues:
CWE-89: Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’) – CVE-2015-6537
A SQL command may be inserted into the login page URL, causing the unauthenticated user to be logged in as an administrator. This issue affects only Cardio Server version 3.3.
CWE-90: Improper Neutralization of Special Elements used in an LDAP Query (‘LDAP Injection’) – CVE-2015-6538
An LDAP query may be inserted into the login page URL, causing Cardio Server to perform an LDAP query to the IP address of the attacker’s choice. This issues affects only Cardio Server versions 3.3, 4.0, and 4.1.
Epiphany has provided a statement detailing these issues, more information about affected versions and how to obtain packages.
An attacker on the local network may be able to bypass authentication, and access and modify patient information.
Apply an update
Epiphany Healthcare has released patches for the affected Cardio Server versions 3.3, 4.0, and 4.1. Users are encouraged to apply the patches as soon as possible, and consider updating to the latest version of Cardio Server.
In Epiphany’s statement, the following information was provided:
Please contact Epiphany’s Vice President of Professional Services, Kelli Sudduth, with any questions you may have, including requesting patches for your Cardio Server. Kelli’s number is: (919) 354-5050 or email@example.com.
Vendor Information (Learn More)
VendorStatusDate NotifiedDate UpdatedEpiphany HealthcareAffected14 Oct 201509 Dec 2015If you are a vendor and your product is affected, let
CVSS Metrics (Learn More)
Thanks to Alex Lauerman of TrustFoundry for reporting this vulnerability.
This document was written by Garret Wassermann.
30 Nov 2015
Date First Published:
01 Dec 2015
Date Last Updated:
09 Dec 2015
FeedbackIf you have feedback, comments, or additional information about this vulnerability, please send us email.