CVE-2020-11533
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 · uneditedIvanti Workspace Control before 10.4.30.0, when SCCM integration is enabled, allows local users to obtain sensitive information (keying material).
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 version 10.4.30.0 contains a vulnerability when SCCM (System Center Configuration Manager) integration is enabled, allowing local users to obtain sensitive keying material such as encryption keys or authentication credentials used for SCCM communication. This is an information disclosure vulnerability requiring local access to the 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< 10.4.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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Verify Ivanti Workspace Control is installedCheck for Ivanti Workspace Control in the system: Look in Add/Remove Programs (Windows), check for the application in Program Files, or query the installed software inventory. Note the exact version number installed.Affected if Version is present and is lower than 10.4.30.0
-
Confirm the vulnerable version rangeCompare your installed version to the affected range. If the version is 10.4.30.0 or later, the vulnerability has been patched. If it is below 10.4.30.0, the version falls within the affected range.Affected if Installed version is less than 10.4.30.0
-
Determine if SCCM integration is enabledInspect the Ivanti Workspace Control configuration settings or management console. Look for SCCM (System Center Configuration Manager) integration settings. This is typically found in the workspace control admin interface, configuration files, or registry settings related to SCCM/ConfigMgr integration.Affected if SCCM integration is enabled and the version is vulnerable (less than 10.4.30.0)
-
Check for stored SCCM credentials or keysIf you have access, examine the Ivanti Workspace Control data stores, configuration directories, or encrypted credential storage for SCCM-related entries. The vulnerability specifically exposes encryption keys or authentication credentials used for SCCM communication.Affected if SCCM credentials or encryption keys are stored and accessible within the application data directories while running a vulnerable version with SCCM enabled
You are affected if Ivanti Workspace Control version is below 10.4.30.0 AND SCCM integration is currently enabled, as this is the specific configuration that exposes sensitive keying material to local users.
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.
From vendor data10.4.30.0
Upgrade Ivanti Workspace Control to version 10.4.30.0 or later. Until upgrade, consider disabling SCCM integration if not required, and restrict physical and logical access to affected workstations.
- 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-2020-11533 — 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-2020-11533 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