CVE-2017-11614
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 · uneditedMEDHOST Connex contains hard-coded credentials that are used for customer database access. An attacker with knowledge of the hard-coded credentials and the ability to communicate directly with the database may be able to obtain or modify sensitive patient and financial information. Connex utilizes an IBM i DB2 user account for database access. The account name is HMSCXPDN. Its password is hard-coded in multiple places in the application. Customers do not have the option to change this password. The account has elevated DB2 roles, and can access all objects or database tables on the customer DB2 database. This account can access data through ODBC, FTP, and TELNET. Customers without Connex installed are still vulnerable because the MEDHOST setup program creates this account.
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 confidenceMEDHOST Connex contains hard-coded credentials (IBM i DB2 account HMSCXPDN with hard-coded password) embedded in multiple places within the application. This account has elevated DB2 roles granting full access to all database tables containing sensitive patient and financial information, accessible via ODBC, FTP, and TELNET protocols.
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 dataall versionsCVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Medhost Connex installationSearch the system for Medhost Connex application files, services, or directories. Check Program Files, Program Data, or custom installation paths commonly used for healthcare applications.Affected if Medhost Connex software is found installed on the system
-
Locate embedded credentials in application filesSearch configuration files, scripts, and application directories for the hard-coded username HMSCXPDN. Use file content search tools to find this specific username string within .ini, .cfg, .xml, .config, .properties, or script files.Affected if The username HMSCXPDN is found hard-coded in any configuration or script file
-
Inspect ODBC data source configurationsReview ODBC Data Source Administrator configurations on servers running Medhost Connex. Check both System DSN and File DSN entries for connections to IBM i DB2 that may use embedded credentials.Affected if ODBC connections to DB2 are configured using the hard-coded HMSCXPDN account
-
Check for FTP/TELNET access to DB2Review network configurations, firewall rules, and application documentation to determine if FTP or TELNET protocols are enabled for accessing the IBM i DB2 database from Medhost Connex.Affected if FTP or TELNET access to the DB2 database is permitted and the hard-coded account is used for authentication
-
Audit database account privilegesIf database access is available, query the IBM i DB2 system to enumerate accounts and check if HMSCXPDN exists with elevated roles and full access to patient or financial data tables.Affected if The HMSCXPDN account exists in DB2 with elevated privileges and access to sensitive tables
The environment is affected if Medhost Connex is installed and the hard-coded HMSCXPDN account with known credentials is present and accessible via ODBC, FTP, or TELNET protocols.
Generated from the published advisory. Verify against your own configuration.
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 dataContact MEDHOST for an official patch to remove or allow customer-controlled rotation of hard-coded credentials. In the interim, implement network segmentation and firewall rules to restrict access to the DB2 database to only authorized application servers and administrative workstations.
- Consultation12.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $16,896.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11614 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-11614 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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