CVE-2017-11693
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 Document Management System 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. PostgreSQL is used as the Document Management System database. The account name is dms. The password is hard-coded throughout the application, and is the same across all installations. Customers do not have the option to change passwords. The dms account for PostgreSQL has access to the database schema for Document Management System.
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 Document Management System contains a hard-coded PostgreSQL database credential (username: dms) that is identical across all installations and cannot be changed by customers. This allows any attacker with knowledge of these credentials to directly access the database and obtain or modify sensitive patient health information and financial data.
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
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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.
-
Identify Medhost Document Management System installationCheck installed applications or running services for 'Medhost Document Management System' or 'Medhost DMS' using system inventory tools, service listings, or application directoriesAffected if The product is present on the system
-
Locate the PostgreSQL configuration filesSearch for PostgreSQL connection configuration files within the Medhost DMS installation directory, typically named postgresql.conf, pg_hba.conf, or application configuration files containing database connection stringsAffected if Configuration files contain hardcoded credentials with username 'dms'
-
Verify database connectivity with default credentialsAttempt to connect to the PostgreSQL database using the known credentials (username: dms, password as documented in CVE details) or examine connection strings in configuration files for plaintext credentialsAffected if Connection succeeds using hardcoded credentials or credentials are found in plaintext configuration
-
Check if credentials can be changedReview application settings, admin interfaces, or documentation for options to modify the database password; attempt to change the dms user password through available interfacesAffected if No option exists to change the database credentials or changes are not persistent across updates
If Medhost Document Management System is installed, the environment is affected because all installations share identical, unchangeable hardcoded database credentials.
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 dataImplement a secure, configurable credential management system that allows customers to set unique passwords, remove hard-coded credentials from the application codebase, and rotate the default credentials. This requires a vendor patch or significant code modification.
- Consultation12.0 h
- Implementation24.0 h
- Testing12.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 $15,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11693 — 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-11693 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