CVE-2017-17424
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 NVBUScheduleSet 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-4235.
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 NVBUScheduleSet Get method of Quest NetVault Backup 11.3.0.12 allows remote unauthenticated attackers to execute arbitrary code by supplying malicious input that is not validated before being used in SQL query construction.
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 NetVault Backup installationCheck for Quest NetVault Backup installation by looking in program directories (typically C:\Program Files\Quest\NetVault Backup or /opt/quest/netvault) and check the version information in the main application or via command: nvtsan -version or through the web interface login pageAffected if Quest NetVault Backup is not installed or version differs from 11.3.0.12
-
Confirm exact version numberLocate the exact version file or use the application's About/Version information panel. Common paths: Installation directory or registry entry HKLM\SOFTWARE\Quest\NetVault\Backup\CurrentVersionAffected if Version is anything other than 11.3.0.12 exactly
-
Determine web interface exposureCheck if the NetVault Backup web service (default port 8443 or 8080) is listening and accessible from network. Run netstat or check firewall rules to determine if port 8443/8080 is exposed to untrusted networksAffected if Web interface is exposed to untrusted networks (internet or less trusted LAN segments)
-
Identify vulnerable endpoint accessibilityVerify the NVBUScheduleSet API endpoint exists and is reachable via HTTP to the web interface. This is typically at /cgi-bin/nvbackup.exe/NVBUScheduleSet or similar CGI path under the web serviceAffected if NVBUScheduleSet endpoint is accessible without authentication
Affected if running exactly version 11.3.0.12 of Quest NetVault Backup with the web interface and NVBUScheduleSet endpoint exposed to untrusted access
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 patch immediately. If no patch is available, restrict network exposure of the NetVault Backup service and deploy WAF/IPS rules to detect SQL injection attack patterns in HTTP requests.
- Consultation4.0 h
- Implementation8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17424 — 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-17424 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