CVE-2017-17422
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 · uneditedThis vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Quest NetVault Backup 11.3.0.12. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of NVBUBackup Get method requests. The issue results from the lack of proper validation of a user-supplied string before using it to construct SQL queries. An attacker can leverage this vulnerability to execute code in the context of the underlying database. Was ZDI-CAN-4233.
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 critical SQL injection vulnerability in Quest NetVault Backup 11.3.0.12 allows unauthenticated remote attackers to execute arbitrary code via the NVBUBackup Get method. The flaw stems from improper validation of user-supplied strings before using them in SQL query construction, enabling attackers to inject malicious SQL statements and execute code in the database context.
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= 11.3.0.12CVSS 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.
-
Verify Quest NetVault Backup is installedLocate the NetVault Backup installation on the system, typically found in Program Files/Quest/NetVault Backup or via system inventory toolsAffected if NetVault Backup software is present on the system
-
Check installed NetVault Backup versionUse the application's version information dialog, check the About section in the NetVault Backup console, or query the installed software registry/manifestAffected if The installed version is exactly 11.3.0.12
-
Confirm NVBUBackup service accessibilityIdentify if the NVBUBackup web service or API endpoint is exposed and accessible on the networkAffected if The NVBUBackup interface is reachable from the network (unauthenticated)
-
Inspect web service configurationReview the NetVault Backup web server configuration to determine if the NVBUBackup Get method is enabled and accessible without authenticationAffected if The NVBUBackup Get method is enabled and accepts unauthenticated requests
A system is affected if Quest NetVault Backup version 11.3.0.12 is installed and the NVBUBackup web service endpoint is accessible, allowing unauthenticated SQL injection via the Get method.
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.
dbcve · scopedApply vendor patches for NetVault Backup 11.3.0.12 and implement parameterized queries with proper input validation for all user-supplied data in NVBUBackup methods. If no patch available, consider network segmentation to limit exposure.
Latest available NetVault Backup version (contact Quest Support for exact version number containing the CVE-2017-17422 fix)
- Identify the current NetVault Backup version by checking the About or Version information in the NetVault Backup web interface or command-line tools
- Contact Quest Software Technical Support to obtain the specific patched version for NetVault Backup that addresses CVE-2017-17422
- Alternatively, download the latest available NetVault Backup version from the Quest Software Support website (support.quest.com) which should contain fixes for this vulnerability
- Before upgrading, backup the NetVault Backup configuration and database
- Stop the NetVault Backup services before performing the upgrade
- Install the patched or upgraded version following Quest's standard upgrade documentation
- Restart NetVault Backup services after installation
- Verify the NVBUBackup Get method functionality works correctly and that the SQL injection vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17422 — 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-17422 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