dbcve.org
ZimbraApplication

CVE-2023-38750

HIGH · 7.5 CVSS v3.1 Published 2023-07-31
Fix available
A fix is available. Upgrade to 8.8.15 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
In Zimbra Collaboration (ZCS) 8 before 8.8.15 Patch 41, 9 before 9.0.0 Patch 34, and 10 before 10.0.2, internal JSP and XML files can be exposed.

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 confidence

Zimbra Collaboration Suite allows unauthenticated access to internal JSP and XML files, potentially exposing sensitive application code, configuration details, and internal paths. This information disclosure could aid attackers in further exploitation of the system.

MitigationApply the vendor-released patches for the affected versions (8.8.15 Patch 41, 9.0.0 Patch 34, or 10.0.2) to restrict access to internal files.

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
ZimbraApplication
Affected:>= 8.8.0, < 8.8.15= 8.8.15= 9.0.0= 10.0.1

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Zimbra version
    Run 'zmcontrol -v' or check /opt/zimbra/.install_history for the version string
    Affected if The version falls within >= 8.8.0 and < 8.8.15, equals 8.8.15, 9.0.0, or 10.0.1
  2. Identify accessible internal endpoints
    Attempt to access common internal paths such as /res/I18nMsg,AjxCache,ZimbraBranding.css and /service/extension/lua/webblobs or similar internal JSP/XML endpoints without authentication
    Affected if The server returns internal JSP or XML content without requiring authentication credentials
  3. Check for exposed configuration files
    Probe for exposed files like /zimbraAdmin/ or /public/ artifacts that may reveal internal paths or application configuration details without credentials
    Affected if Sensitive configuration or path information is returned in the response without authentication
  4. Verify patch installation status
    Check /opt/zimbra/.patchingstate or examine the installed patches via 'zmpatch -l' to see if the relevant security patches are applied
    Affected if No security patches (such as Patch 41 for 8.8.15, Patch 34 for 9.0.0, or Patch 2 for 10.0.2) are installed on the affected version

The environment is affected if the installed Zimbra version is 8.8.0 through 8.8.15, 9.0.0, or 10.0.1 and internal JSP/XML files are accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 8.8.15 or later
Fixed in 8.8.15
Interim mitigation

Apply the vendor-released patches for the affected versions (8.8.15 Patch 41, 9.0.0 Patch 34, or 10.0.2) to restrict access to internal files.

Recommended fix High confidence

Upgrade to ZCS 8.8.15 Patch 41+, ZCS 9.0.0 Patch 34+, or ZCS 10.0.2+ depending on your current branch

  1. 1. Identify the current Zimbra Collaboration (ZCS) version in use by checking the /opt/zimbra/.git_description file or running 'zmcontrol -v'
  2. 2. Determine which branch (8.x, 9.x, or 10.x) the current installation belongs to
  3. 3. For ZCS 8.x (versions 8.8.0 through 8.8.15): Upgrade to ZCS 8.8.15 Patch 41 or later
  4. 4. For ZCS 9.x (version 9.0.0): Upgrade to ZCS 9.0.0 Patch 34 or later
  5. 5. For ZCS 10.x (version 10.0.1): Upgrade to ZCS 10.0.2 or later
  6. 6. Review the Zimbra wiki for specific patch installation instructions for your version and platform
  7. 7. Perform a full backup of the Zimbra mail store and configuration before applying any upgrade
  8. 8. Test the upgrade in a non-production environment before deploying to production
Caveat Standard Zimbra upgrade risks apply - ensure backups are verified and test thoroughly in staging before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zimbra Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-38750 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-38750 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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