dbcve.org
DosewiseApplication · Philips

CVE-2017-9656

CRITICAL · 9.1 CVSS v3.0 Published 2018-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The backend database of the Philips DoseWise Portal application versions 1.1.7.333 and 2.1.1.3069 uses hard-coded credentials for a database account with privileges that can affect confidentiality, integrity, and availability of the database. For an attacker to exploit this vulnerability, elevated privileges are first required for an attacker to access the web application backend system files that contain the hard-coded credentials. Successful exploitation may allow a remote attacker to gain access to the database of the DWP application, which contains PHI. CVSS v3 base score: 9.1, CVSS vector string: AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Philips DoseWise Portal application versions 1.1.7.333 and 2.1.1.3069 contains hard-coded credentials embedded in backend system files for a database account. An attacker with elevated privileges who can access these files can retrieve the credentials and then gain unauthorized access to the application's database, which contains Protected Health Information (PHI).

MitigationReplace hard-coded database credentials with dynamically managed, strong credentials and implement proper secret management. Restrict access to backend system files and update to patched versions if available from Philips.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DosewiseApplication
Affected:= 1.1.7.333= 2.1.1.3069

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Philips DoseWise Portal installation
    Locate the DoseWise Portal application on the system. Check for installation directories or running services associated with the product.
    Affected if The application is installed on the system.
  2. Identify installed version
    Use system utilities or application metadata to determine the installed version of Philips DoseWise Portal. Compare against the affected versions 1.1.7.333 and 2.1.1.3069.
    Affected if The installed version matches exactly 1.1.7.333 or 2.1.1.3069.
  3. Locate backend system files
    Search for configuration, script, or backend files associated with DoseWise Portal installation, including database connection configuration files and backend service scripts.
    Affected if Backend system files exist in the application directory structure.
  4. Inspect for hard-coded credentials
    Open and examine the identified backend system files. Search for embedded plaintext credentials, password fields, or connection strings that contain database authentication details.
    Affected if Hard-coded credentials for a database account are found embedded in backend system files.
  5. Check file access controls
    Review file permissions on backend system files to determine if unprivileged users or attackers with elevated privileges could read sensitive configuration files.
    Affected if Backend files containing credentials have weak permissions allowing unauthorized read access.

A system is affected if Philips DoseWise Portal version 1.1.7.333 or 2.1.1.3069 is installed and backend system files contain hard-coded database credentials accessible to unauthorized users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace hard-coded database credentials with dynamically managed, strong credentials and implement proper secret management. Restrict access to backend system files and update to patched versions if available from Philips.

Fix this in Dosewise Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-9656 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-9656 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data