# CVE-2017-5598: SQL injection in n/a

> Unauthenticated attackers can exploit blind SQL injection in the EmployeePortalServlet to dump database data via out-of-band techniques.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jan 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r34p-x9w8-7458

## What is CVE-2017-5598?

CVE-2017-5598 is a high-severity SQL injection vulnerability in n/a, published on 27 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in eClinicalWorks healow@work 8.0 build 8. This is a blind SQL injection within the EmployeePortalServlet, which can be exploited by un-authenticated users via an HTTP POST request and which can be used to dump database data out to a malicious server, using an out-of-band technique, such as select_loadfile(). The vulnerability affects the EmployeePortalServlet page and the following parameter: employer.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Eclinicalworks Patient Portal.

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

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

## Is CVE-2017-5598 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-5569](https://insights.sbomify.com/CVE-2017-5569/): SQL injection in n/a (critical 9.8)
- [CVE-2017-5570](https://insights.sbomify.com/CVE-2017-5570/): SQL injection in n/a (high 8.8)
- [CVE-2017-5599](https://insights.sbomify.com/CVE-2017-5599/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-5598 is a high-severity SQL injection vulnerability in n/a, published on 27 Jan 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-5598 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-5598/ (Markdown: https://insights.sbomify.com/CVE-2017-5598/index.md)
```

## Sources

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

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