CVE-2020-35123
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 · uneditedIn Zimbra Collaboration Suite Network Edition versions < 9.0.0 P10 and 8.8.15 P17, there exists an XXE vulnerability in the saml consumer store extension, which is vulnerable to XXE attacks. This has been fixed in Zimbra Collaboration Suite Network edition 9.0.0 Patch 10 and 8.8.15 Patch 17.
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 confidenceZimbra Collaboration Suite Network Edition contains an XML External Entity (XXE) vulnerability in the SAML consumer store extension. The vulnerability allows attackers to inject malicious XML entities into SAML authentication requests, potentially enabling disclosure of sensitive files or server-side request forgery. The flaw exists in versions prior to 9.0.0 Patch 10 and 8.8.15 Patch 17.
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> 8.8.0, < 8.8.15= 8.8.15= 9.0.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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/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.
-
Identify Zimbra installation and versionRun 'zmcontrol -v' or 'zmcontrol status' from the /opt/zimbra directory to retrieve the installed ZCS versionAffected if Version is 8.8.1 through 8.8.15 (any patch), or 9.0.0 (any patch before P10)
-
Confirm exact patch levelCheck the localconfig.xml file at /opt/zimbra/conf/localconfig.xml for the 'zimbra_version' or 'patch_version' attribute, or run 'zmcontrol -v' which displays the full version and patch levelAffected if Version shows 9.0.0 without Patch 10, or 8.8.15 without Patch 17, or falls in the 8.8.1-8.8.14 range
-
Determine if SAML authentication is enabledReview the Zimbra admin console for SAML/SSO configuration, or inspect the ZCS configuration files in /opt/zimbra/java/usr/share/tomcat/webapps/ for SAML-related XML configuration files under the web.xml or associated SAML consumer directoriesAffected if SAML authentication is configured or the SAML consumer store extension is present in the ZCS environment
-
Verify SAML consumer store extension presenceInspect the /opt/zimbra directory for the SAML consumer store extension JAR files or configuration, typically found within the Jetty or Tomcat webapp directories used by ZCSAffected if The SAML consumer store extension is installed as part of the ZCS Network Edition installation
A ZCS installation is affected if it runs version 8.8.1 through 8.8.15 or version 9.0.0 prior to Patch 10, and has SAML authentication or the SAML consumer store extension enabled.
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 data8.8.15
Apply the vendor-supplied patches (ZCS 9.0.0 P10 or 8.8.15 P17) to remediate this vulnerability. If immediate patching is not possible, consider restricting access to the SAML consumer endpoint or disabling SAML authentication until the patch can be applied.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35123 — 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-35123 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