CVE-2021-27767
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 · uneditedThe BigFix Console 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 confidenceThe BigFix Console installer was built using InstallShield, which contained CVE-2021-41526 - a local privilege escalation vulnerability allowing a local attacker to gain elevated privileges during the installation process. The vendor resolved this by rebuilding the installer with a patched version of InstallShield.
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>= 9.5, <= 9.5.18>= 10, <= 10.0.5CVSS 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.
-
Locate the BigFix Console installerSearch for installer files matching 'BigFix*Console*.exe' or 'BESConsole*.exe' in software distribution folders, download directories, or installation media repositoriesAffected if The installer file exists and was used for installation
-
Check installer versionRight-click the installer .exe file, select Properties, and view the Version tab for the File Version or Product Version fieldAffected if The version falls within 9.5 through 9.5.18 OR 10.0 through 10.0.5
-
Check InstallShield version in installerOpen the installer in a tool that can extract InstallShield project information, or check the installer manifest for the InstallShield build versionAffected if The InstallShield version corresponds to the build that contains CVE-2021-41526 (vulnerable InstallShield version)
-
Review installation logsCheck installation logs in the BigFix logs directory or Windows Temp folder for InstallShield version strings like 'InstallShield' or 'ISSetup'Affected if Logs show an InstallShield version known to be affected by CVE-2021-41526
You are affected if you used a BigFix Console installer with version 9.5-9.5.18 or 10.0-10.0.5, as these were built with the vulnerable InstallShield version containing CVE-2021-41526.
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 · scopedOrganizations should obtain and use the updated BigFix Console installer version that was rebuilt with the patched InstallShield version to ensure the privilege escalation vector is eliminated.
BigFix Platform 9.5.19 or later, or BigFix Platform 10.0.6 or later
- 1. Identify the current BigFix Platform version by checking the BigFix console or server
- 2. If running version 9.5.x and <= 9.5.18, upgrade to version 9.5.19 or later
- 3. If running version 10.0.x and <= 10.0.5, upgrade to version 10.0.6 or later
- 4. Verify the upgrade completed successfully by checking the BigFix server version
- 5. Ensure the BigFix Console is reinstalled with the updated installer to receive the patched InstallShield components
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-27767 — 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-2021-27767 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