dbcve.org
ZimbraApplication

CVE-2024-9665

MEDIUM · 6.5 CVSS v3.1 Published 2024-11-22
Fix available
A fix is available. Upgrade to 9.0.0 / 10.0.10 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Zimbra GraphQL Cross-Site Request Forgery Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of Zimbra. User interaction is required to exploit this vulnerability in that the target must open a malicious email message. The specific flaw exists within the implementation of the graphql endpoint. The issue results from the lack of proper protections against cross-site request forgery (CSRF) attacks. An attacker can leverage this vulnerability to disclose information in the context of the target email account. Was ZDI-CAN-23939.

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

The vulnerability exists in Zimbra's GraphQL endpoint which lacks CSRF protection. An attacker can embed malicious requests in an email that, when opened by a victim, causes the victim's authenticated browser to execute unintended GraphQL queries, exposing sensitive email account data.

MitigationImplement CSRF token validation on the GraphQL endpoint, ensuring requests include valid tokens tied to user sessions.

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:< 9.0.0>= 10.0.0, < 10.0.10>= 10.1.0, < 10.1.2= 9.0.0

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Identify installed Zimbra version
    Run 'zmcontrol -v' or check /opt/zimbra/.version file to determine the installed Zimbra version
    Affected if Version falls into ranges: < 9.0.0, 9.0.0, 10.0.0-10.0.9, or 10.1.0-10.1.1
  2. Verify GraphQL endpoint is exposed
    Check if the /graphql or /service/graphql endpoint responds on your Zimbra server (e.g., curl https://yourserver/graphql)
    Affected if GraphQL endpoint is accessible and responds to requests without requiring additional authentication beyond user session
  3. Check for CSRF token validation on GraphQL requests
    Inspect HTTP headers and request parameters for CSRF tokens when making GraphQL queries; examine if the endpoint rejects requests without a valid 'X-Zimbra-CSRF' or similar token header
    Affected if GraphQL endpoint accepts and processes requests without validating CSRF tokens, allowing cross-origin requests to execute authenticated queries
  4. Review browser-based email rendering settings
    Check if users render HTML emails in the Zimbra web client, which would enable automatic execution of embedded malicious requests
    Affected if HTML email rendering is enabled in the Zimbra web client, allowing embedded requests to trigger automatically when users open crafted emails

Your environment is affected if you run a Zimbra version in the ranges listed and the GraphQL endpoint accepts requests without CSRF token validation, particularly if users access email through the web client.

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 9.0.0 / 10.0.10 / 10.1.2 or later
Fixed in 9.0.010.0.1010.1.2
Interim mitigation

Implement CSRF token validation on the GraphQL endpoint, ensuring requests include valid tokens tied to user sessions.

Recommended fix Moderate confidence

10.0.10 or 10.1.2 (depending on major version branch)

  1. 1. Identify the current Zimbra version by running: zmcontrol -v or checking the Zimbra admin console
  2. 2. Based on current version, plan upgrade path: If running 9.0.0.x, upgrade to 9.0.0 patch 31 or later (or migrate to 10.x); If running 10.0.x (where x < 10), upgrade to 10.0.10 or later; If running 10.1.0 or 10.1.1, upgrade to 10.1.2 or later
  3. 3. Review Zimbra upgrade documentation at https://zimbra.github.io/documentation/ for your current version
  4. 4. Perform a full backup of the Zimbra mailbox and configuration before upgrading
  5. 5. Test the upgrade in a staging environment before applying to production
  6. 6. Apply the upgrade following Zimbra's standard upgrade procedures
  7. 7. Verify the GraphQL endpoint now includes CSRF protection by checking that requests require a valid CSRF token
Caveat Upgrading between major Zimbra versions (9.x to 10.x) may require migration steps and compatibility checks with existing configurations and integrations

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

Fix this in Zimbra Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9665 — 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-2024-9665 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