CVE-2022-23156
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 · uneditedWyse Device Agent version 14.6.1.4 and below contain an Improper Authentication vulnerability. A malicious user could potentially exploit this vulnerability by providing invalid input in order to obtain a connection to WMS server.
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 confidenceWyse Device Agent versions 14.6.1.4 and below contain an improper authentication vulnerability where the application fails to properly validate input during WMS server connection attempts. A malicious user could exploit this by providing invalid input to obtain an authenticated connection to the WMS server, bypassing proper authentication controls.
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<= 14.6.1.4CVSS 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.
-
Confirm Wyse Device Agent installationLocate the Wyse Device Agent installation directory or check installed programs list. Common paths include C:\Program Files\Wyse\Device Agent\ or C:\Program Files (x86)\Wyse\Device Agent\Affected if Wyse Device Agent is not found on the system, the vulnerability does not apply.
-
Determine installed versionCheck the version of Wyse Device Agent by right-clicking the executable file (usually DeviceAgent.exe or WDA.exe), selecting Properties, and viewing the Details tab for the Product Version. Alternatively, check Add/Remove Programs for the installed version.Affected if The installed version is 14.6.1.4 or any version lower (e.g., 14.6.0.x, 13.x.x.x). Versions at or below 14.6.1.4 are affected.
-
Check WMS server connection configurationExamine the Wyse Device Agent configuration files (commonly found in the config or settings subfolder within the installation directory, or in the Windows registry under HKLM\SOFTWARE\Wyse\Device Agent) for WMS server connection settings.Affected if A WMS server address is configured or the WMS connection feature is enabled, making the improper authentication vulnerability reachable.
-
Review WMS connection logsInspect Wyse Device Agent logs (typically in a logs subfolder within the installation directory or in Windows Event Viewer under Application logs) for WMS connection attempts and authentication events.Affected if Logs show connection attempts to WMS servers, confirming the vulnerable feature is in use.
A system is affected if Wyse Device Agent version 14.6.1.4 or lower is installed and WMS server connection functionality is configured or active.
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 dataUpgrade Wyse Device Agent to a version newer than 14.6.1.4. Additionally, restrict network access to WMS servers and implement additional monitoring for suspicious connection attempts.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23156 — 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-23156 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