# CVE-2017-11614: Hardcoded credentials in n/a

> Hard-coded database credentials in MEDHOST Connex allow attackers to access and modify sensitive patient and financial data.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jul 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-f789-6fmg-9xhj

## What is CVE-2017-11614?

CVE-2017-11614 is a critical vulnerability in n/a, published on 25 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MEDHOST 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.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Medhost Connex.

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

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

## Is CVE-2017-11614 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-11743](https://insights.sbomify.com/CVE-2017-11743/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-11614 is a critical vulnerability in n/a, published on 25 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-11614 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-11614/ (Markdown: https://insights.sbomify.com/CVE-2017-11614/index.md)
```

## Sources

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

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