Your one-stop web resource providing safety and security information to manufacturers

Philips has an update available to handle cross-site scripting and information exposure vulnerabilities in its Tasy EMR, according to a report with CISA.

Successful exploitation of these vulnerabilities could impact or compromise patient confidentiality and system integrity. Philips’ analysis has shown these issues, if fully exploited, may allow an attacker of low skill to provide unexpected input into the application, execute arbitrary code, alter the intended control flow of the system, and access sensitive information. This an update to a previous notice from last April.

Security researcher Rafael Honorato reported and Unimed de Blumenau Cooperativa de Trabalho Médico IT Department each separately reported a vulnerability to Philips.

The following versions of Tasy EMR, a clinical and administrative workflow-based information system, are affected:
• Tasy EMR Versions 3.02.1744 and prior
• Tasy WebPortal Versions 3.02.1757 and prior

Schneider Bold

In one vulnerability, the software incorrectly neutralizes user-controllable input before it is placed in output used as a web page that is served to other users.

CVE-2019-6562 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 4.1.

In addition, there is an information exposure vulnerability which may allow a remote attacker to access system and configuration information.

CVE-2019-13557 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 4.3.

The product sees use mainly in the healthcare and public health sectors. It also sees action in Brazil and Mexico.

No known public exploits specifically target these vulnerabilities.

Philips advises users to update to the most recently released versions of the product, following the Tasy EMR release schedule. Update Tasy EMR, to version 3.03.1745 or higher and update Tasy WebPortal, to version 3.03.1758 or higher.

Philips also recommends users follow the instructions in the product configuration manual and follow market standard best practices from the application server manufacturer documentation related to security.

Users should upgrade Service Packs as soon as possible. Hosted solutions will end up patched automatically. Users running the application on premise are always alerted via release notes on changes to the system.

Pin It on Pinterest

Share This