dbcve.org
Workforce AccessApplication · Hypr

CVE-2023-6335

HIGH · 7.8 CVSS v3.1 Published 2024-01-16
Fix available
A fix is available. Upgrade to 8.7 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Improper Link Resolution Before File Access ('Link Following') vulnerability in HYPR Workforce Access on Windows allows User-Controlled Filename.This issue affects Workforce Access: before 8.7.

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 confidence

This is a Time-of-Check-Time-of-Use (TOCTOU) vulnerability where HYPR Workforce Access on Windows performs file operations using user-controlled filenames without properly validating or resolving symbolic links first. An attacker could potentially craft a malicious symlink to access or overwrite sensitive files outside the intended directory.

MitigationUpgrade HYPR Workforce Access to version 8.7 or later which contains the fix for this improper link resolution vulnerability.

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
Workforce AccessApplication
Affected:< 8.7

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify HYPR Workforce Access is installed
    Check for the presence of HYPR Workforce Access installation on the Windows system. Look for the application in Program Files, Program Files (x86), or check the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for HYPR Workforce Access entry.
    Affected if The application is installed on the system
  2. Determine the installed version
    Locate the version information of HYPR Workforce Access. This is typically found in the application's executable file properties (right-click the main .exe file, go to Details tab), or in the Windows registry under the Uninstall key mentioned above.
    Affected if The installed version is lower than 8.7 (e.g., 8.6, 8.5, earlier versions)
  3. Identify file operation configurations
    Review HYPR Workforce Access configuration files or logs that involve file operations with user-supplied filenames. Look for features that process, import, export, or manipulate files based on user input.
    Affected if The application uses user-controlled filenames in file operations without explicit symlink validation in the code or configuration
  4. Check for symbolic link usage
    Examine the application's behavior when processing file paths. Observe if the application resolves symbolic links before performing file operations, or if it directly operates on the path provided.
    Affected if The application performs file operations on paths without validating whether they are symbolic links first

The environment is affected if HYPR Workforce Access is installed with a version lower than 8.7 and the application performs file operations using user-controlled filenames without proper symlink validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 8.7 or later
Fixed in 8.7
Interim mitigation

Upgrade HYPR Workforce Access to version 8.7 or later which contains the fix for this improper link resolution vulnerability.

Recommended fix Moderate confidence

Workforce Access version 8.7 or later

  1. Verify the current installed version of HYPR Workforce Access by checking the application or system information
  2. Backup any local configuration or data as a precautionary measure
  3. Download the latest version of HYPR Workforce Access (version 8.7 or later) from the official HYPR website or your organization's software distribution channel
  4. Run the installer with appropriate administrative privileges
  5. Follow the on-screen prompts to complete the upgrade installation
  6. Restart the workstation if required by the installer
  7. Verify the upgrade was successful by checking that the version now shows 8.7 or later
Caveat Review HYPR release notes for any configuration changes or migration requirements between your current version and 8.7

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Workforce Access Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6335 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-6335 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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