CVE-2017-16733
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 · uneditedA SQL Injection issue was discovered in Ecava IntegraXor v 6.1.1030.1 and prior. The SQL Injection vulnerability has been identified, which an attacker can leverage to disclose sensitive information from the database.
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 · moderate confidenceSQL Injection vulnerability in Ecava IntegraXor v6.1.1030.1 and prior allows unauthenticated attackers to inject malicious SQL queries via unspecified input fields, potentially exposing sensitive data stored in the connected database.
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<= 6.1.1030.1CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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.
-
Verify Ecava IntegraXor is installedCheck for the application in typical installation directories such as C:\Program Files\Ecava\IntegraXor or C:\Program Files (x86)\Ecava\IntegraXor, or look for the service named 'IntegraXor' in Windows Services.Affected if The application is found on the system
-
Locate the installed versionOpen the folder where IntegraXor is installed and locate a version file, readme, or the main executable properties. The version may also be visible in the Windows Services list entry for IntegraXor.Affected if No version information can be located or the version is 6.1.1030.1 or earlier
-
Compare version against affected rangeCompare the identified version number to the affected range: 6.1.1030.1 and prior. If the exact version cannot be determined, check for any version file or release notes in the installation directory.Affected if The installed version is 6.1.1030.1 or any earlier version (for example, 6.1.1029.0, 6.0.x, etc.)
-
Determine if the web interface is accessibleIf IntegraXor is running, verify whether the web-based SCADA interface is accessible from the network. This is typically served on port 8080 or 80. Attempt to access the login page or any input field.Affected if The IntegraXor web interface is exposed to network users and the version is within the affected range
The environment is affected if Ecava IntegraXor version 6.1.1030.1 or any prior version is installed and the application or its web interface is accessible.
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 dataApply vendor-supplied patch or update to IntegraXor version 6.1.1030.2 or later; implement input validation and parameterized queries as defense-in-depth.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-16733 — 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-16733 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