CVE-2022-23922
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 Announcer directory and elevate permissions whenever the program is executed.
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 local privilege escalation vulnerability due to a permissions misconfiguration on the Program Announcer directory. An attacker with local access can write arbitrary files to this directory, which are then executed with elevated privileges whenever the WIN-911 program runs.
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 or check the WIN-911 application properties to determine the currently installed version numberAffected if The installed version matches 5.21.10 (2021 R1) or 5.21.17 (2021 R2)
-
Locate the Program Announcer directorySearch the WIN-911 installation directory for a folder named Program Announcer or subdirectories containing the word AnnouncerAffected if The Program Announcer directory exists within the WIN-911 installation path
-
Verify directory permissionsRight-click the Program Announcer folder, select Properties, then go to the Security tab to view assigned users and their permissionsAffected if Standard user accounts or non-admin groups are listed with Write or Modify permissions to this directory
-
Test write access as unprivileged userAttempt to create a test file in the Program Announcer directory using an account that does not have administrator privilegesAffected if The unprivileged user can successfully create or modify files in this directory
You are affected if WIN-911 2021 R1 (5.21.10) or R2 (5.21.17) is installed AND the Program Announcer directory grants write access to standard (non-privileged) user accounts.
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 · scopedRestrict write permissions on the Program Announcer directory to only privileged/system accounts, removing access for standard users and untrusted processes.
Win 911 2021 R1 or R2 to latest vendor-provided patched version (contact vendor for specific version number)
- 1. Identify the current installed version of Win 911 by checking Program Files or the application's about/info section
- 2. Obtain the latest version of Win 911 from the vendor's official support channel (supportdesk.win911.com)
- 3. Before upgrading, back up all Win 911 configuration files and databases
- 4. Uninstall the current version of Win 911 2021 R1 (5.21.10) or R2 (5.21.17)
- 5. Verify that all files in the Program Announcer directory have been removed
- 6. Install the vendor-provided patched version that addresses the permissions vulnerability
- 7. After installation, verify that the Program Announcer directory has restrictive permissions (only SYSTEM, Administrators, and the application service account should have write access)
- 8. Test that Win 911 functions normally after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- 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-23922 — 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-23922 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