CVE-2020-35682
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 · uneditedZoho ManageEngine ServiceDesk Plus before 11134 allows an Authentication Bypass (only during SAML login).
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 confidenceZoho ManageEngine ServiceDesk Plus versions before 11134 contain an authentication bypass vulnerability that specifically occurs during SAML login. This allows attackers to potentially bypass authentication mechanisms and gain unauthorized access to the application when SAML authentication is configured.
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< 11.1= 11.1CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 the ServiceDesk Plus versionAccess the ServiceDesk Plus admin console and navigate to 'Admin' > 'About' to view the build number and version, or check the buildinfo.txt file in the installation directoryAffected if The displayed version is 11.1 or any build number below 11134
-
Verify SAML authentication is configuredNavigate to 'Admin' > 'Authentication' > 'SAML SSO' in the admin console to check if SAML login has been configured and enabledAffected if SAML authentication is enabled and configured as an authentication method
-
Confirm the build number directlyIn the ServiceDesk Plus installation directory, locate and open the 'buildnum.txt' or 'buildinfo.txt' file to read the exact build numberAffected if The build number is 11133 or lower (indicating a version before the fix)
-
Check for SAML-specific configuration filesExamine the SAML configuration files in the ServiceDesk Plus installation directory, typically found in the 'conf' or 'saml' subdirectories, for active SAML provider settingsAffected if SAML configuration files exist and contain active Identity Provider (IdP) settings
You are affected if your ServiceDesk Plus version shows build 11133 or lower AND SAML authentication is configured and enabled in your environment.
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 data11.1
Upgrade ManageEngine ServiceDesk Plus to version 11134 or later. If immediate upgrade is not feasible, review and audit SAML configuration, consider disabling SAML login temporarily, and implement additional access controls.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35682 — 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-35682 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