# CVE-2019-13557: Information disclosure in Tasy EMR

> Remote attackers can access sensitive system and configuration information in Tasy EMR WebPortal, exposing critical data to unauthorized users.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q62p-7qmj-cm9r

## What is CVE-2019-13557?

CVE-2019-13557 is a medium-severity vulnerability in Tasy EMR, published on 8 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Tasy EMR, Tasy WebPortal Versions 3.02.1757 and prior, there is an information exposure vulnerability which may allow a remote attacker to access system and configuration information.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2019-13557?

It affects 2 products.


Products: Philips Tasy Emr, Philips Tasy Webportal.

## How do I fix CVE-2019-13557?

No fix has been published for CVE-2019-13557 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-13557 being exploited?

There is no known exploitation of CVE-2019-13557 in the wild and no public exploit code.

## Other vulnerabilities in Tasy EMR

- [CVE-2019-6562](https://insights.sbomify.com/CVE-2019-6562/): Cross-site scripting in Philips Tasy EMR (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-13557 and fix it if it is affected.

What it is: CVE-2019-13557 is a medium-severity vulnerability in Tasy EMR, published on 8 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-13557 in the wild and no public exploit code.

Affected product: Tasy EMR. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-13557/ (Markdown: https://insights.sbomify.com/CVE-2019-13557/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-13557
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-13557
- OSV: https://osv.dev/vulnerability/CVE-2019-13557

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-13557/
Summaries are generated and may contain mistakes; the official description above is the record.