Netvault BackupApplication · Quest

CVE-2018-1162

HIGH · 8.1 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 →
87/100
Remediation priority · High
Remotely reachable 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 create a denial-of-service condition on vulnerable installations of Quest NetVault Backup 11.2.0.13. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be easily bypassed. The specific flaw exists within the handling of Export requests. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to arbitrarily overwrite files resulting in a denial-of-service condition. Was ZDI-CAN-4222.

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 confidence

A path traversal vulnerability in Quest NetVault Backup 11.2.0.13 allows authenticated remote attackers to overwrite arbitrary files via Export requests. The flaw stems from missing validation of user-supplied paths before file operations, combined with an easily bypassable authentication mechanism.

MitigationImplement strict path validation to prevent directory traversal and fix the authentication bypass vulnerability. Restrict file write operations to authorized directories only.

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.2.0.13

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Verify NetVault Backup version
    Check the installed Quest NetVault Backup version by viewing the About section in the management console, or run: nvtypelog -h (or check the installation directory for version.txt/VERSION file)
    Affected if Version is exactly 11.2.0.13
  2. Confirm web service is running
    Check if the NetVault Backup web interface (typically on port 80/443 or 8080/8443) is listening and accessible. Use: netstat -an | grep -E '80|443|8080|8443' or check services.msc for NetVault Web Server
    Affected if Web interface is exposed and reachable
  3. Verify Export feature is enabled
    Check if the Export/Backup-to-Disk or file export functionality is configured and accessible through the web console. Look for Export job types in the job configuration.
    Affected if Export functionality is available and configured
  4. Test authentication bypass condition
    Attempt to access the web API endpoints without valid credentials (e.g., direct API calls to export functions). Check if unauthenticated requests to /rpc/export or similar endpoints are accepted.
    Affected if Unauthenticated or improperly authenticated requests are processed by the Export functionality

You are affected if running Quest NetVault Backup version 11.2.0.13 with the web interface and Export feature enabled, where the authentication bypass allows unauthorized file write operations.

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

Implement strict path validation to prevent directory traversal and fix the authentication bypass vulnerability. Restrict file write operations to authorized directories only.

Fix this in Netvault Backup Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1162 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1162 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