dbcve.org
Snow License ManagerApplication · Snowsoftware

CVE-2022-0883

HIGH · 7.8 CVSS v3.1 Published 2022-05-18
Fix available
A fix is available. Upgrade to 9.20.1 or later.
See remediation →
80/100
Remediation priority · High
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
SLM has an issue with Windows Unquoted/Trusted Service Paths Security Issue. All installations version 9.x.x prior to 9.20.1 should be patched.

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

SLM (Service Layer Manager) contains a Windows Unquoted Service Path vulnerability where service executables are installed in paths with spaces without proper quotation, allowing attackers to potentially execute malicious binaries by placing them in intermediate path directories. This affects all versions 9.x.x prior to version 9.20.1.

MitigationUpgrade SLM to version 9.20.1 or later to resolve the unquoted service path vulnerability. Verify all Windows services use quoted paths in their configuration post-upgrade.

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
Snow License ManagerApplication
Affected:>= 9.0.0, < 9.20.1

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

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

  1. Check installed Snow License Manager version
    Open Windows Registry and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or check Add/Remove Programs for Snow License Manager, or run: wmic product where "name like '%Snow License Manager%'" get version
    Affected if Installed version is 9.0.0 through 9.20.0 (any version >= 9.0.0 and < 9.20.1)
  2. Identify Snow License Manager Windows services
    Open Services console (services.msc) or run: sc query type= service state= all | findstr /i "snow" or: Get-Service | Where-Object {$_.DisplayName -like '*Snow*'}
    Affected if Any SLM-related Windows services exist on the system
  3. Inspect service binary path configuration
    For each SLM service identified, run: sc qc <service_name> and examine the BINARY_PATH_NAME field, or inspect HKLM\SYSTEM\CurrentControlSet\Services\<service_name>\ImagePath
    Affected if The binary path contains spaces and is NOT enclosed in quotation marks
  4. Verify if service path contains spaces
    Parse the BINARY_PATH_NAME from sc qc output - check if the path string contains any space characters and is missing opening and closing quotation marks around the full path
    Affected if Path has spaces without surrounding quotes (e.g., C:\Program Files\Snow Software\Service\service.exe instead of "C:\Program Files\Snow Software\Service\service.exe")

You are affected if Snow License Manager version is 9.0.0 through 9.20.0 and any SLM Windows service has an unquoted binary path containing spaces.

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.

dbcve · scoped
Upgrade available Upgrade to 9.20.1 or later
Fixed in 9.20.1
Interim mitigation

Upgrade SLM to version 9.20.1 or later to resolve the unquoted service path vulnerability. Verify all Windows services use quoted paths in their configuration post-upgrade.

Recommended fix High confidence

9.20.1 or later

  1. Backup your current Snow License Manager installation and database before proceeding
  2. Download Snow License Manager version 9.20.1 or later from the official Snow Software portal or vendor repository
  3. Stop the Snow License Manager service if it's currently running
  4. Install the upgrade following the official Snow License Manager upgrade documentation
  5. Start the Snow License Manager service after installation completes
  6. Verify the service is running and accessible, and confirm the version number in the About or version information

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Snow License Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-0883 — 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-2022-0883 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