CVE-2022-27592
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 search path or element vulnerability has been reported to affect QVR Smart Client. If exploited, the vulnerability could allow local authenticated administrators to execute unauthorized code or commands via unspecified vectors. We have already fixed the vulnerability in the following version: Windows 10 SP1, Windows 11, Mac OS, and Mac M1: QVR Smart Client 2.4.0.0570 and later
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 confidenceThis is an unquoted service path vulnerability in QVR Smart Client on Windows systems. When executable paths containing spaces are not properly quoted, local authenticated administrators could potentially place malicious executables in intermediate directories along the path to achieve arbitrary code execution. The vulnerability is fixed in version 2.4.0.0570.
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>= 2.4.0, < 2.4.0.0570CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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.
-
Identify if QVR Smart Client is installedOpen Windows Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell to list installed software. Look for 'QVR Smart Client' in the program list.Affected if QVR Smart Client appears in the installed programs list
-
Determine the installed version of QVR Smart ClientIn Programs and Features, click on QVR Smart Client to view the version, or check the program directory for a version file. Compare the version number against 2.4.0.0570.Affected if The installed version is 2.4.0 or higher but lower than 2.4.0.0570
-
Inspect Windows services for QVR-related executablesOpen Services console (services.msc) or run 'sc qc' on any QVR-related services. Check the binary path for each service. Look for paths containing spaces that are not enclosed in quotation marks.Affected if A QVR service has a binary path with spaces that is not properly quoted (e.g., C:\Program Files\QVR Smart Client\bin\service.exe instead of "C:\Program Files\QVR Smart Client\bin\service.exe")
-
Verify intermediate directory write accessFor any unquoted service path found, check if intermediate directories along the path are writable by local administrators. Useicacls or File Explorer security properties on each directory in the path.Affected if A local administrator can write to any intermediate directory in the unquoted service path
If QVR Smart Client version is between 2.4.0 and 2.4.0.0569 inclusive AND has an unquoted service path with writable intermediate directories, the system is vulnerable to CVE-2022-27592.
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 · scoped2.4.0.0570
Deploy QVR Smart Client version 2.4.0.0570 or later to all affected client workstations. This is a client-side vulnerability affecting local authenticated administrators, so focus on endpoint patching and inventory of installations.
QVR Smart Client 2.4.0.0570 and later
- 1. Verify the current installed version of QVR Smart Client by opening the application and navigating to Help > About, or checking Add/Remove Programs in Windows or Applications folder on Mac.
- 2. Navigate to the official QNAP website (www.qnap.com) and locate the QVR Smart Client download page.
- 3. Download QVR Smart Client version 2.4.0.0570 or later for your operating system (Windows 10 SP1, Windows 11, Mac OS, or Mac M1).
- 4. Uninstall the current vulnerable version of QVR Smart Client from the system.
- 5. Restart the computer if prompted by the uninstaller.
- 6. Install the newly downloaded QVR Smart Client version 2.4.0.0570 or later.
- 7. After installation, verify the installed version matches 2.4.0.0570 or higher to confirm remediation.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27592 — 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-2022-27592 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