dbcve.org
Netvault BackupApplication · Quest

CVE-2017-17418

CRITICAL · 9.8 CVSS v3.0 Published 2018-02-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
This 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 NVBUPolicy 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-4229.

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 confidence

Unauthenticated SQL injection in the NVBUPolicy Get method of Quest NetVault Backup 11.3.0.12 allows remote attackers to execute arbitrary code by supplying malicious SQL queries via unsanitized user input. The vulnerability stems from direct string concatenation in SQL query construction without proper input validation.

MitigationApply vendor patch for CVE-2017-17418; until then, consider network segmentation to restrict access to NetVault Backup management interfaces and disable the affected NVBUPolicy service if possible.

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
Netvault BackupApplication
Affected:= 11.3.0.12

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify NetVault Backup installation and version
    Check for the presence of Quest NetVault Backup and retrieve the installed version. On Windows, check the Add/Remove Programs list or examine the binary version of the nvbu.exe or related executables in the installation directory. On Linux, check the RPM/DEB package or the version file in /opt/netvault or /usr/local/netvault.
    Affected if The installed version is exactly 11.3.0.12.
  2. Verify the NVBUPolicy service exists
    Check for the presence of the NVBUPolicy service or component. On Windows, use Services.msc or sc query to list services containing 'NVBU' or 'NetVault'. Examine the NetVault Backup installation directory for the Policy component or module.
    Affected if The NVBUPolicy service or policy management component is present and installed.
  3. Confirm the web management interface is enabled
    NetVault Backup typically exposes a web-based management console. Check if the web server component (usually on port 80/443 or custom ports like 20020) is running. Look for the nvwbpnmp.exe or similar web service process, and check listening network ports using netstat -an or similar tools.
    Affected if The NetVault Backup web management interface is running and listening on any network interface.
  4. Assess network exposure of management interface
    Review firewall rules and network configuration to determine if the NetVault Backup management port is accessible from untrusted networks. Use netstat -an or listening port scans to identify bound addresses, and check if the interface is bound to 0.0.0.0 (all interfaces) versus 127.0.0.1 (localhost only).
    Affected if The management interface is listening on a non-loopback address and is accessible from network segments other than trusted management networks.

A system is affected if Quest NetVault Backup version 11.3.0.12 is installed with the NVBUPolicy component and the web management interface is network-accessible, allowing unauthenticated attackers to inject SQL through the NVBUPolicy Get method.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch for CVE-2017-17418; until then, consider network segmentation to restrict access to NetVault Backup management interfaces and disable the affected NVBUPolicy service if possible.

Fix this in Netvault Backup Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-17418 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-17418 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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