dbcve.org
GaroonApplication · Cybozu

CVE-2022-29512

MEDIUM · 6.5 CVSS v3.1 Published 2022-07-11
Fix available
A fix is available. Upgrade to after 5.9.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Exposure of sensitive information to an unauthorized actor issue in multiple applications of Cybozu Garoon 4.0.0 to 5.9.1 allows a remote authenticated attacker to obtain the data without the viewing privilege.

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 confidence

Cybozu Garoon versions 4.0.0 to 5.9.1 contains an information disclosure vulnerability where a remote authenticated attacker can access data without having the required viewing privileges, effectively bypassing authorization controls in multiple applications.

MitigationApply the latest vendor security patch for Cybozu Garoon and conduct a review of access control configurations across all affected modules to ensure proper privilege enforcement.

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:>= 4.0.0, <= 5.9.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
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 checks

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

  1. Identify installed Cybozu Garoon version
    Access the system administration panel or check the Garoon installation directory for version information. Typically found in the 'syslog' or 'admin' section, or via the Garoon login page footer version display.
    Affected if The installed version is 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.1.0, 4.1.1, 4.1.2, 4.2.0, 4.2.1, 4.2.2, 4.2.3, 4.3.0, 4.3.1, 4.3.2, 4.4.0, 4.4.1, 4.4.2, 4.4.3, 4.5.0, 4.5.1, 4.5.2, 4.6.0, 4.6.1, 4.6.2, 4.7.0, 4.7.1, 4.7.2, 4.8.0, 4.8.1, 4.8.2, 4.9.0, 4.9.1, 4.9.2, 4.9.3, 5.0.0, 5.0.1, 5.0.2, 5.1.0, 5.1.1, 5.
  2. Verify Garoon is accessible to authenticated users
    Confirm that user authentication is enabled and users can log into the Garoon system. Check the authentication configuration in the system settings.
    Affected if User authentication is active and external or internal users can log in, providing them an attack vector to exploit the authorization bypass.
  3. Review enabled Garoon applications
    Access the system administration panel and list all enabled applications and modules within Garoon, such as mail, calendar, address book, workflow, or other packaged applications.
    Affected if Multiple applications are enabled, as the vulnerability affects multiple applications within the Garoon suite.
  4. Audit access control configurations
    Examine the permission settings for each enabled application in the Garoon administration panel. Check whether view privileges are properly assigned and enforced for different user roles.
    Affected if Access control settings exist but the vulnerability allows bypassing them, meaning the system relies solely on these configurations which are insufficient without the patch.

You are affected if your Cybozu Garoon installation version falls within 4.0.0 to 5.9.1 and the system has authenticated users or external access enabled.

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 a release after 5.9.1
Interim mitigation

Apply the latest vendor security patch for Cybozu Garoon and conduct a review of access control configurations across all affected modules to ensure proper privilege enforcement.

Recommended fix Moderate confidence

Garoon version > 5.9.1 (contact Cybozu for exact latest patched version)

  1. 1. Back up your current Garoon database and configuration files.
  2. 2. Obtain the latest version of Garoon from Cybozu's official download page or contact their support (cs.cybozu.co.jp).
  3. 3. Plan your upgrade path, considering testing in a staging environment first.
  4. 4. Run the upgrade installer following Cybozu's standard upgrade procedure.
  5. 5. After upgrade, verify that the vulnerability is resolved by testing access controls on affected applications.
Caveat Review Cybozu's release notes for version 5.9.2+ for any compatibility changes or deprecated features before upgrading.

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

Fix this in Garoon Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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