# CVE-2017-9654: Hardcoded credentials in DoseWise Portal

> Attackers can read clear-text login credentials from backend files, compromising user accounts in the Philips DoseWise Portal.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-8582-989r-ww9v

## What is CVE-2017-9654?

CVE-2017-9654 is a high-severity vulnerability in Philips DoseWise Portal, published on 24 Apr 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Philips DoseWise Portal web-based application versions 1.1.7.333 and 2.1.1.3069 stores login credentials in clear text within backend system files. CVSS v3 base score: 6.5, CVSS vector string: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 1 product.


Products: Philips Dosewise.

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

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

## Is CVE-2017-9654 being exploited?

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

## Other vulnerabilities in Philips DoseWise Portal

- [CVE-2017-9656](https://insights.sbomify.com/CVE-2017-9656/): Hardcoded credentials in DoseWise Portal (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9654 is a high-severity vulnerability in Philips DoseWise Portal, published on 24 Apr 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-9654 in the wild and no public exploit code.

Affected product: Philips DoseWise Portal. 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-9654/ (Markdown: https://insights.sbomify.com/CVE-2017-9654/index.md)
```

## Sources

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

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