Bigfix PlatformApplication · Hcltech

CVE-2021-27766

HIGH · 7.8 CVSS v3.1 Published 2022-05-06
Fix available
A fix is available. Upgrade to after 10.0.5 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
The BigFix Client installer is created with InstallShield, which was affected by CVE-2021-41526, a vulnerability that could allow a local user to perform a privilege escalation. This vulnerability was resolved by updating to an InstallShield version with the underlying vulnerability fixed.

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

The BigFix Client installer is built with InstallShield, which contains CVE-2021-41526 vulnerability. This flaw allows a local unprivileged user to perform privilege escalation during or after the installation process, potentially gaining SYSTEM-level access.

MitigationRebuild the BigFix Client installer using a version of InstallShield that incorporates the CVE-2021-41526 fix, then distribute the updated installer to replace vulnerable versions.

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
Bigfix PlatformApplication
Affected:>= 9.5, <= 9.5.18>= 10, <= 10.0.5

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 BigFix Client version
    Open Windows Registry and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{BFD8B610-2C88-4D2A-9D0E-2B4A3E7A562F} (or search for BigFix in Uninstall registry), or run 'bigfix.exe -version' from the BigFix client directory
    Affected if Version is >= 9.5 and <= 9.5.18, or >= 10.0 and <= 10.0.5
  2. Identify BigFix installer files on system
    Search for installer files: look for 'BigFix Windows Client.exe', 'BESClient-*.msi', or similar installer files in common locations such as C:\Program Files\BigFix, C:\Users\*\Downloads, or shared installer repositories
    Affected if Installer files exist on the system that were created with vulnerable InstallShield versions
  3. Check for unauthorized SYSTEM-level processes
    Open Task Manager or run 'tasklist /v' and look for processes running under the SYSTEM account that were not initiated by an administrator, or check Event Viewer Security logs for new accounts created or privilege escalation events around installation times
    Affected if SYSTEM-level processes exist or privilege escalation events occurred that correlate with BigFix installation timing

A system is affected if the BigFix Client version falls within 9.5 through 9.5.18 or 10.0 through 10.0.5, or if installer files built with vulnerable InstallShield versions are present on the system.

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 a release after 10.0.5
Interim mitigation

Rebuild the BigFix Client installer using a version of InstallShield that incorporates the CVE-2021-41526 fix, then distribute the updated installer to replace vulnerable versions.

Recommended fix Moderate confidence

BigFix Platform 10.0.6 or later (10.x), or 9.5.19 or later (9.5.x)

  1. Upgrade BigFix Platform to version 10.0.6 or later for the 10.x release line
  2. Alternatively, upgrade to version 9.5.19 or later for the 9.5.x release line
  3. After upgrading, verify the BigFix Client installer uses a patched InstallShield version by reviewing release notes or contacting HCL/BigFix support

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

Fix this in Bigfix Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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