CVE-2017-5570
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 · uneditedAn issue was discovered in eClinicalWorks Patient Portal 7.0 build 13. This is a blind SQL injection within the messageJson.jsp, which can only be exploited by 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().
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 confidenceA blind SQL injection vulnerability exists in eClinicalWorks Patient Portal 7.0 build 13 within the messageJson.jsp component. The vulnerability is authenticated (requires valid user credentials), exploited via HTTP POST requests, and allows attackers to execute arbitrary SQL queries using blind injection techniques with out-of-band data exfiltration via select_loadfile(). This enables complete database compromise including patient health information.
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= 7.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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.
-
Identify eClinicalWorks Patient Portal versionCheck the installed version of eClinicalWorks Patient Portal in the application or system documentation. This is typically visible in the login page footer, about page, or installation records.Affected if The installed version is exactly 7.0 (build 13 specifically mentioned)
-
Locate messageJson.jsp componentCheck if the file messageJson.jsp exists in the web application's accessible directories, typically under the patient portal web root.Affected if The messageJson.jsp file exists in the deployed web application
-
Verify portal is accessible over networkConfirm the eClinicalWorks Patient Portal web interface is reachable via HTTP/HTTPS on the expected port (commonly port 80/443 or custom web server port).Affected if The patient portal web interface is network-accessible
-
Confirm authentication mechanismDetermine whether valid user credentials can be obtained for the portal. The vulnerability requires authenticated access.Affected if User accounts exist and login is possible (even with low-privilege credentials)
A user is affected if they have eClinicalWorks Patient Portal version 7.0 deployed with the messageJson.jsp component accessible and user authentication is possible.
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 parameterized queries or prepared statements for all database interactions in messageJson.jsp, apply strict input validation on all user-supplied parameters, and enforce least-privilege database accounts to limit the impact of any successful SQL injection.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5570 — 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-5570 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