Summaryinfo

A vulnerability classified as critical has been found in Epic MyChart. Affected is an unknown function of the file help.asp. The manipulation of the argument topic as part of Parameter leads to xml injection. This vulnerability is traded as CVE-2016-6272. It is possible to launch the attack remotely. Furthermore, there is an exploit available. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Detailsinfo

A vulnerability was found in Epic MyChart (unknown version). It has been rated as critical. This issue affects an unknown code block of the file help.asp. The manipulation of the argument topic as part of a Parameter leads to a xml injection vulnerability. Using CWE to declare the problem leads to CWE-91. The product does not properly neutralize special elements that are used in XML, allowing attackers to modify the syntax, content, or commands of the XML before it is processed by an end system. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

SQL injection vulnerability in EPIC MyChart allows remote attackers to execute arbitrary SQL commands via the topic parameter to help.asp.

The bug was discovered 08/19/2016. The weakness was published 02/20/2018 as EDB-ID 44098 as not defined exploit (Exploit-DB). It is possible to read the advisory at exploit-db.com. The identification of this vulnerability is CVE-2016-6272 since 07/22/2016. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

After immediately, there has been an exploit disclosed. The exploit is available at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 550 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:help.asp it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Exploit-DB (44098). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Epic

Name

• MyChart

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion