CVE-2021-36235
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 · uneditedAn issue was discovered in Ivanti Workspace Control before 10.6.30.0. A locally authenticated user with low privileges can bypass File and Folder Security by leveraging an unspecified attack vector. As a result, the attacker can start applications with elevated privileges.
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 confidenceIvanti Workspace Control before 10.6.30.0 contains a privilege escalation vulnerability where a locally authenticated low-privilege user can bypass File and Folder Security restrictions using an unspecified attack vector, enabling the attacker to launch applications with elevated privileges.
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< 10.6.30.0CVSS 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.
-
Check Ivanti Workspace Control versionOpen the application and navigate to Help > About, or check the version displayed in the workspace control administration console. The version number is typically visible in the main window title bar or in the system tray icon properties.Affected if The installed version is earlier than 10.6.30.0 (for example, 10.6.20.0, 10.5.x, or earlier)
-
Verify File and Folder Security is in useIn the Ivanti Workspace Control administration console, navigate to Security > File and Folder Security (or the equivalent section for your version). Check if any security rules are defined or if the feature is enabled.Affected if File and Folder Security is enabled and the installed version is below 10.6.30.0
-
Review configured application launch rulesIn the administration console, check Application Launcher or Security settings for rules that restrict which applications users can run. Look for rules that should block elevated privilege execution.Affected if Application launch restrictions exist and the installed version is below 10.6.30.0
-
Audit local user accounts on the systemOpen Computer Management > Local Users and Groups > Users to enumerate local accounts. Check for standard or limited user accounts that could be exploited.Affected if Local low-privilege user accounts exist and the installed version is below 10.6.30.0
A system is affected if Ivanti Workspace Control version is below 10.6.30.0 and File and Folder Security or application launch restrictions are in use with local user access.
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 · scoped10.6.30.0
Upgrade Ivanti Workspace Control to version 10.6.30.0 or later. Until the upgrade is applied, limit local user account creation and monitor for unauthorized application execution.
10.6.30.0 or later
- Verify the current installed version of Ivanti Workspace Control in your environment
- Contact Ivanti support or access the official Ivanti customer portal to obtain version 10.6.30.0 or a later stable release
- Review release notes and upgrade documentation for any prerequisites or specific procedures
- Test the upgrade in a non-production environment before deploying to production
- Deploy the upgrade to production systems following standard change management procedures
- Verify that the upgrade was successful and that File and Folder Security controls are functioning as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-36235 — 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-36235 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