CVE-2022-44264
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 · uneditedDentsply Sirona Sidexis <= 4.3 is vulnerable to Unquoted Service Path.
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 confidenceDentsply Sirona Sidexis <= 4.3 contains a Windows service with an unquoted executable path. This vulnerability allows an attacker with low-privilege access to potentially escalate privileges by placing a malicious executable in an intermediate directory along the unquoted path.
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.3CVSS 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.
-
Identify installed Sidexis versionOpen Windows Control Panel, navigate to Programs and Features, and look for 'Dentsply Sirona Sidexis' in the list of installed software. Note the version number displayed.Affected if The version shown is 4.3 or lower (or if the version cannot be determined but Sidexis software is present)
-
Enumerate Sidexis Windows servicesOpen Command Prompt as a low-privilege user and run: 'sc queryex type= service state= all' to list all services, then filter for Sidexis-related entries using: 'sc queryex type= service state= all | findstr /i sidexis'Affected if Any service with 'Sidexis' in its name or description is found
-
Check service executable path for unquoted spacesFor each Sidexis service identified, run: 'sc qc [ServiceName]' (for example, 'sc qc SidexisService') and examine the BINARY_PATH_NAME field in the output.Affected if The BINARY_PATH_NAME contains spaces and is not enclosed in quotation marks (e.g., C:\Program Files\Dentsply Sirona\Sidexis\bin\service.exe instead of "C:\Program Files\Dentsply Sirona\Sidexis\bin\service.exe")
-
Verify path contains intermediate directoriesFrom the BINARY_PATH_NAME identified in step 3, note each directory segment separated by backslashes. Check if any directory name in the path contains a space.Affected if The path has at least one directory with a space in its name (e.g., 'Program Files' or 'Dentsply Sirona') and is not quoted
Your environment is affected if Dentsply Sirona Sidexis version 4.3 or lower is installed AND a Sidexis-related Windows service has an unquoted executable path containing spaces in any intermediate directory name.
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 dataLocate the affected service(s), identify the unquoted path, and either enclose the path in quotes within the service configuration or remove/reorganize directories in the path to eliminate spaces.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44264 — 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-44264 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