SafeqApplication · Ysoft

CVE-2021-31859

HIGH · 7.8 CVSS v3.1 Published 2021-07-14
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
Incorrect privileges in the MU55 FlexiSpooler service in YSoft SafeQ 6 6.0.55 allows local user privilege escalation by overwriting the executable file via an alternative data stream.

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

The MU55 FlexiSpooler service in YSoft SafeQ 6 version 6.0.55 runs with elevated Windows service privileges but has incorrect file permissions that allow a low-privileged local user to overwrite the service executable file via a Windows Alternate Data Stream (ADS). This enables local privilege escalation from a standard user to SYSTEM-level access.

MitigationApply the vendor patch when available; in the interim, audit and correct NTFS file permissions on the FlexiSpooler service executable to prevent unauthorized modification by non-admin users, and restrict local access to the affected system.

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.55

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 YSoft SafeQ 6 version
    Check the installed version of YSoft SafeQ on the system using the vendor's standard version detection method or check Add/Remove Programs for 'YSoft SafeQ' version 6.0.55
    Affected if YSoft SafeQ version 6.0.55 is installed
  2. Locate FlexiSpooler service
    Open Windows Services console (services.msc) and search for a service named 'MU55 FlexiSpooler' or 'FlexiSpooler', or run 'sc query' to enumerate services and find one containing 'FlexiSpooler'
    Affected if The FlexiSpooler service exists on the system
  3. Identify service executable path
    Right-click the FlexiSpooler service, select Properties, and note the path to the executable file shown in 'Path to executable'
    Affected if The service executable path is identified
  4. Check NTFS permissions on service executable
    Right-click the service executable file, select Properties > Security tab, then check the permissions for standard users or the 'Users' group. Specifically verify if Write or Modify permissions are granted to non-admin accounts
    Affected if Standard non-admin users have Write or Modify permissions to the service executable file
  5. Test write access via ADS
    As a low-privilege standard user (not administrator), attempt to create a Windows Alternate Data Stream on the FlexiSpooler service executable using a command such as 'echo test > "<path to service exe>:test.txt"'
    Affected if A standard user can successfully create an Alternate Data Stream on the service executable, indicating exploitable permissions

A system is affected if YSoft SafeQ version 6.0.55 is installed with the FlexiSpooler service, and non-administrative users have write permissions to the service executable file.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch when available; in the interim, audit and correct NTFS file permissions on the FlexiSpooler service executable to prevent unauthorized modification by non-admin users, and restrict local access to the affected system.

Fix this in Safeq Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-31859 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-31859 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