CVE-2019-7201
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 · uneditedAn unquoted service path vulnerability is reported to affect the service QVssService in QNAP NetBak Replicator. This vulnerability could allow an authorized but non-privileged local user to execute arbitrary code with elevated system privileges. QNAP have already fixed this issue in QNAP NetBak Replicator 4.5.12.1108.
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 confidenceAn unquoted service path vulnerability exists in the QVssService of QNAP NetBak Replicator. When service executable paths contain spaces and are not properly quoted, Windows may attempt to execute intermediate path components as executables. This allows a local non-privileged user to potentially place a malicious executable in an intermediate path location that gets executed with SYSTEM-level privileges when the service starts.
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<= 4.5.11.816CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Check NetBak Replicator versionOpen Programs and Features (appwiz.cpl) or check the installation directory for NetBak Replicator version information. Look for the installed version in the program list or check the executable version details.Affected if Installed version is 4.5.11.816 or lower (the affected version range).
-
Locate QVssService in Windows servicesOpen Services console (services.msc) or run 'sc query QVssService' command to find the QVssService service.Affected if The QVssService exists and is listed in Windows services.
-
Check service binary path in registryOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\QVssService, then examine the ImagePath value. Alternatively, run 'sc qc QVssService' command.Affected if The ImagePath value contains spaces and is not enclosed in quotation marks.
-
Verify executable path componentsInspect the unquoted path from the ImagePath value. Identify all directory components in the path that contain spaces (for example: C:\Program Files\QNAP\NetBak Replicator\QVssService.exe).Affected if The path contains spaces and is unquoted, meaning intermediate path components could be exploited.
You are affected if NetBak Replicator version is 4.5.11.816 or lower AND the QVssService exists with an unquoted binary path containing spaces.
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 dataUpgrade QNAP NetBak Replicator to version 4.5.12.1108 or later, which contains the vendor fix. Alternatively, manually correct the service binary path in Windows registry to include proper quotes around the executable path.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7201 — 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-2019-7201 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