dbcve.org
GaroonApplication · Cybozu

CVE-2024-31400

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-11
Fix available
A fix is available. Upgrade to 6.0.0 or later.
See remediation →
74/100
Remediation priority · Elevated
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
Insertion of sensitive information into sent data issue exists in Cybozu Garoon 5.0.0 to 5.15.0. If this vulnerability is exploited, unintended data may be left in forwarded mail.

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

A data leakage vulnerability in Cybozu Garoon versions 5.0.0 to 5.15.0 allows sensitive information to be inadvertently included in forwarded emails. When mail is forwarded, unintended data from previous correspondence or system metadata may remain attached or embedded, potentially exposing confidential content to external recipients.

MitigationApply the vendor patch or upgrade to a Cybozu Garoon version beyond 5.15.0 when available. Until then, review and sanitize any forwarded mail content manually, and consider implementing additional email filtering controls to inspect outgoing messages.

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
GaroonApplication
Affected:>= 5.5.0, < 6.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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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. Confirm Cybozu Garoon installation
    Check if Cybozu Garoon is installed by looking for the product in your system inventory, or access the Garoon admin console by navigating to the web interface and reviewing the system information.
    Affected if Cybozu Garoon is present in the environment
  2. Identify installed Garoon version
    Access the Garoon admin console and navigate to System Settings > System Information to view the exact version number, or check the product documentation for the installed version location.
    Affected if The installed version is >= 5.5.0 and < 6.0.0, or falls within 5.0.0 to 5.15.0 range
  3. Verify mail forwarding feature usage
    Review Garoon's mail settings in the administration panel under Mail > Forwarding or similar mail configuration sections to determine if mail forwarding is enabled or configured.
    Affected if Mail forwarding is enabled and used to send emails to external recipients
  4. Inspect outgoing mail configuration
    Check the mail routing and forwarding rules in Garoon's admin console under Mail settings to see if automatic forwarding to external addresses is configured.
    Affected if Forwarding rules direct mail to external/destination addresses outside the organization
  5. Audit recent forwarded emails
    Review mail logs or the sent mail archive in Garoon to identify forwarded messages and check if they contain unexpected attachment content or metadata from previous correspondence.
    Affected if Forwarded emails contain unintended data from prior messages or hidden metadata

You are affected if Cybozu Garoon version 5.5.0 through 5.15.0 (or >= 5.0.0 to < 6.0.0) is installed and the mail forwarding feature is used to forward emails to external recipients.

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 6.0.0 or later
Fixed in 6.0.0
Interim mitigation

Apply the vendor patch or upgrade to a Cybozu Garoon version beyond 5.15.0 when available. Until then, review and sanitize any forwarded mail content manually, and consider implementing additional email filtering controls to inspect outgoing messages.

Recommended fix High confidence

Garoon 6.0.0 or later

  1. Back up your current Garoon installation and database before proceeding with any upgrade.
  2. Confirm current installed version by accessing Garoon's system administration screen.
  3. Download the updated version (6.0.0 or later) from the official Cybozu download page or your licensed distribution channel.
  4. Review the release notes for version 6.0.0 to confirm the security fix for CVE-2024-31400 is included.
  5. Apply the upgrade in a non-production environment first to validate compatibility with your system configuration.
  6. Execute the upgrade following the standard Cybozu Garoon upgrade procedure.
  7. After upgrade, verify the fix by testing forwarded mail functionality to confirm no unintended data remains.
Caveat Review version 6.0.0 release notes for any configuration or compatibility changes from version 5.x; major version upgrades may include feature changes requiring user training.

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

Fix this in Garoon Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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