dbcve.org
SafeqApplication · Ysoft

CVE-2022-38176

HIGH · 7.8 CVSS v3.1 Published 2022-09-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
An issue was discovered in YSoft SAFEQ 6 before 6.0.72. Incorrect privileges were configured as part of the installer package for the Client V3 services, allowing for local user privilege escalation by overwriting the executable file via an alternative data stream. NOTE: this is not the same as CVE-2021-31859.

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 confidence

YSoft SAFEQ 6 before version 6.0.72 ships with incorrectly configured privileges in the Client V3 service installer package, allowing local authenticated users to escalate privileges by overwriting executable files via Windows Alternative Data Streams (ADS). The vulnerability stems from the installer setting overly permissive file permissions that permit standard users to replace service executables.

MitigationUpgrade YSoft SAFEQ to version 6.0.72 or later. As a compensating control, restrict file system permissions on the Client V3 service directory to prevent standard users from modifying executable files.

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
SafeqApplication
Affected:= 6.0

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. Check installed YSoft SAFEQ version
    Locate the YSoft SAFEQ installation and retrieve its version information. This is typically found in Add/Remove Programs, the application itself, or installation directories.
    Affected if The installed version is 6.0.x and is lower than 6.0.72
  2. Identify Client V3 service installation
    Check for the presence of the YSoft SAFEQ Client V3 service on the system. This may appear as a Windows service or be listed within the SAFEQ installation directories.
    Affected if The Client V3 service component is installed on the system
  3. Verify file permissions on service executable directory
    Examine the file system permissions on directories containing YSoft SAFEQ Client V3 service executables. Check if standard user accounts have Write or Modify permissions that allow overwriting executable files.
    Affected if Standard (non-admin) users have permissions to modify, overwrite, or delete service executables in the Client V3 service directories
  4. Check for Alternative Data Streams on service files
    Use Windows commands such as 'dir /r' or PowerShell to inspect service executable files for any attached Alternative Data Streams that may indicate tampering or misconfiguration.
    Affected if Service executables have unexpected ADS attachments or permissions allow standard users to create ADS on these files

A system is affected if YSoft SAFEQ version 6.0.x below 6.0.72 is installed with the Client V3 service, and standard users have write access to the service executable directories allowing privilege escalation via file replacement.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade YSoft SAFEQ to version 6.0.72 or later. As a compensating control, restrict file system permissions on the Client V3 service directory to prevent standard users from modifying executable files.

Recommended fix High confidence

6.0.72 or later (within the 6.x release line)

  1. Backup the current SAFEQ configuration and database before proceeding with the upgrade
  2. Download YSoft SAFEQ version 6.0.72 or later from the official YSoft download portal at www.ysoft.com
  3. Review the official YSoft SAFEQ upgrade documentation for version 6.0.72
  4. Stop the SAFEQ services before applying the upgrade
  5. Apply the upgrade installer following YSoft's standard upgrade procedure
  6. Start the SAFEQ services after the upgrade completes
  7. Verify that the Client V3 services are running with correct privileges
  8. Confirm the vulnerability is remediated by verifying file permissions on executable files no longer allow alternative data stream exploitation

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

Fix this in Safeq Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38176 — 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-2022-38176 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