CVE-2018-1000631
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 · uneditedBattelle V2I Hub 3.0 is vulnerable to SQL injection. A remote attacker could send specially-crafted SQL statements to the tmx/TmxCtl/src/lib/PluginStatus.cpp and TmxControl::user_info() function, which could allow the attacker to view, add, modify or delete information in the back-end 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 · high confidenceSQL injection vulnerability in the TmxControl::user_info() function within tmx/TmxCtl/src/lib/PluginStatus.cpp of Battelle V2I Hub 3.0 allows remote attackers to inject arbitrary SQL statements via unsanitized user input, potentially enabling full database compromise.
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= 3.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 if Battelle V2I Hub is installedLocate the V2I Hub installation directory, typically under /opt/v2i-hub or C:\Program Files\V2IHub on Windows systems. Check for the presence of the tmx/TmxCtl directory structure.Affected if The Battelle V2I Hub software is present on the system
-
Verify the installed version is 3.0Check the version of the V2I Hub installation by reviewing version files, about dialogs, or running 'v2ihub --version' if a CLI tool exists. Cross-reference with any package manager or installer logs.Affected if The installed version is exactly 3.0 (no other versions are affected)
-
Locate the vulnerable PluginStatus.cpp fileSearch for the file tmx/TmxCtl/src/lib/PluginStatus.cpp within the installation directory. If the source code is not present, check for the compiled library (PluginStatus.so or PluginStatus.dll).Affected if The file tmx/TmxCtl/src/lib/PluginStatus.cpp or its compiled binary exists in the installation
-
Confirm the user_info() function is accessibleReview application logs, configuration files, or API endpoints to determine if the TmxControl::user_info() function is exposed as a web service, API, or CLI command that accepts user-supplied input.Affected if The user_info() function is exposed and accepts user-supplied parameters
A system is affected only if Battelle V2I Hub version 3.0 is installed and the TmxControl::user_info() function in PluginStatus.cpp is accessible with user-supplied input reaching it.
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 (prepared statements) or input validation/sanitization for all user-supplied data in the user_info() function and conduct a broader code review for similar injection points in PluginStatus.cpp and related components.
- Consultation6.0 h
- Implementation16.0 h
- Testing8.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 $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000631 — 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-2018-1000631 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