CVE-2022-23104
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 · uneditedWIN-911 2021 R1 and R2 are vulnerable to a permissions misconfiguration that may allow an attacker to locally write files to the program Operator Workspace directory, which holds DLL files and executables. A low-privilege attacker could write a malicious DLL file to the Operator Workspace directory to achieve privilege escalation and the permissions of the user running the program.
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 confidenceWIN-911 2021 R1 and R2 contain a permissions misconfiguration allowing low-privilege local attackers to write files to the Operator Workspace directory, which stores DLL files and executables. By placing a malicious DLL in this directory, an attacker can achieve privilege escalation to the permissions of the user running the WIN-911 service.
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= 5.21.10= 5.21.17CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 WIN-911 versionUse system inventory tools, check registry keys, or examine the WIN-911 application properties to determine the exact version numberAffected if Version is 5.21.10 (2021 R1) or 5.21.17 (2021 R2)
-
Locate the Operator Workspace directorySearch for the directory named 'Operator Workspace' or 'Workspace' within the WIN-911 installation folder, typically found under the main application directoryAffected if The Operator Workspace directory exists on the system
-
Check write permissions on the Operator Workspace directoryRight-click the Operator Workspace folder, go to Properties > Security tab, and review the permissions for standard users or low-privilege accounts. Use icacls or Get-Acl cmdlet to enumerate granted write accessAffected if Low-privilege users or non-admin accounts have Write or Modify permissions to this directory
-
Identify DLL files in the Operator Workspace directoryList all .dll and .exe files within the Operator Workspace directory using dir or Get-ChildItemAffected if The directory contains DLL files or executables that could be replaced with malicious versions
A system is affected if it runs WIN-911 version 5.21.10 or 5.21.17 AND the Operator Workspace directory grants write access to low-privilege users and contains loadable DLL or executable files.
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 dataRestrict write permissions on the Operator Workspace directory to authorized administrators only, removing write access for low-privilege users. Validate that legitimate application functionality does not require user-write access to this directory.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23104 — 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-23104 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