# CVE-2017-14111: Information disclosure in n/a

> Attackers can read domain credentials from workstation logs to access the application and other user entitlements.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-544p-g5p3-4c55

## What is CVE-2017-14111?

CVE-2017-14111 is a high-severity vulnerability in n/a, published on 17 Nov 2017. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The workstation logging function in Philips IntelliSpace Cardiovascular (ISCV) 2.3.0 and earlier and Xcelera R4.1L1 and earlier records domain authentication credentials, which if accessed allows an attacker to use credentials to access the application, or other user entitlements.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2017-14111?

It affects 2 products.


Products: Philips Intellispace Cardiovascular, Philips Xcelera.

## How do I fix CVE-2017-14111?

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

## Is CVE-2017-14111 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-14787](https://insights.sbomify.com/CVE-2018-14787/): Privilege escalation in IntelliSpace Cardiovascular (ISCV) products (high 7.8)
- [CVE-2018-14789](https://insights.sbomify.com/CVE-2018-14789/): Privilege escalation in IntelliSpace Cardiovascular (ISCV) products (medium 6.7)
- [CVE-2018-5438](https://insights.sbomify.com/CVE-2018-5438/): Auth bypass in n/a (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-14111 and fix it if it is affected.

What it is: CVE-2017-14111 is a high-severity vulnerability in n/a, published on 17 Nov 2017. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-14111 in the wild and no public exploit code.

Affected product: n/a. 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-2017-14111/ (Markdown: https://insights.sbomify.com/CVE-2017-14111/index.md)
```

## Sources

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

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