CVE-2022-1984
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 · uneditedThis issue affects: HYPR Windows WFA versions prior to 7.2; Unsafe Deserialization vulnerability in HYPR Workforce Access (WFA) before version 7.2 may allow local authenticated attackers to elevate privileges via a malicious serialized payload.
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 confidenceHYPR Workforce Access (WFA) for Windows versions prior to 7.2 contains an unsafe deserialization vulnerability. A local authenticated attacker can craft a malicious serialized payload that, when deserialized by the application without proper validation, allows arbitrary code execution leading to privilege escalation from standard user to elevated privileges.
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< 7.3.0CVSS 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.
-
Verify HYPR Workforce Access is installedCheck for the presence of HYPR WFA in the Windows Program Files directory, typically at C:\Program Files\HYPR\Workforce Access or C:\Program Files (x86)\HYPR\Workforce Access. Alternatively, check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for HYPR Workforce Access.Affected if HYPR Workforce Access is found on the system.
-
Determine installed version of HYPR WFAOpen Windows Control Panel > Programs and Features, locate HYPR Workforce Access, and view the Version column. Alternatively, check the uninstall registry key mentioned above for the DisplayVersion value.Affected if The installed version is lower than 7.3.0 (e.g., 7.2.x, 7.1.x, or earlier).
-
Confirm current user privilege levelOpen Command Prompt and run 'whoami /groups' to list group memberships. Look for membership in Administrators, Domain Admins, or equivalent elevated groups.Affected if The current user is a standard (non-privileged) user and HYPR WFA is running or configured to run with elevated privileges.
-
Check if HYPR WFA service runs with elevated privilegesOpen Services console (services.msc), locate the HYPR Workforce Access service, right-click and select Properties. Check the 'Log On' tab to see if the service runs as LocalSystem, a service account, or a specific user with elevated privileges.Affected if The HYPR WFA service runs as LocalSystem or another account with administrative privileges, and the installed version is below 7.3.0.
The environment is affected if HYPR Workforce Access is installed with a version lower than 7.3.0 and the application or service runs with elevated privileges that a standard user could potentially escalate to via deserialization attacks.
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 · scoped7.3.0
Upgrade HYPR WFA to version 7.2 or later to remediate this vulnerability.
HYPR Workforce Access 7.3.0
- Download HYPR Workforce Access version 7.3.0 or later from the official HYPR support portal
- Backup the current WFA installation and configuration data
- Install version 7.3.0 or newer following the standard HYPR upgrade documentation
- Verify the upgrade was successful by checking the WFA version in the admin console
- Confirm the service is running properly and users can authenticate
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1984 — 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-1984 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