CVE-2022-30602
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 · uneditedOperation restriction bypass in multiple applications of Cybozu Garoon 4.0.0 to 5.9.1 allows a remote authenticated attacker to alter the file information and/or delete the files.
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 confidenceCybozu Garoon versions 4.0.0 through 5.9.1 contain an operation restriction bypass vulnerability in multiple applications. A remote authenticated attacker can exploit this flaw to alter file metadata and/or delete files outside their authorized scope, indicating a broken access control vulnerability in the file management functionality.
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>= 4.0.0, <= 5.9.1CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
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 the installed Cybozu Garoon versionAccess the system administration panel or check the product information page within Cybozu Garoon to determine the exact version number running in your environmentAffected if The installed version falls within the range 4.0.0 through 5.9.1 (inclusive)
-
Verify if file management applications are activeCheck the Cybozu Garoon system configuration to determine which applications are enabled, specifically looking for file management, bulletin board, or workflow modules that handle file attachments and metadataAffected if File management or related applications that handle file attachments are enabled on the system
-
Review user access control configurationsExamine the permission settings for file management features in the administration console to see how user access boundaries are definedAffected if Multiple users or groups exist with differentiated permissions to files, and the system relies on these access controls to restrict file operations
You are affected if Cybozu Garoon version 4.0.0 through 5.9.1 is running AND file management functionality is enabled, as the vulnerability allows authorized users to bypass intended access restrictions on file metadata modifications or deletions.
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.
dbcve · scopedUpdate Cybozu Garoon to the latest patched version to remediate this authorization bypass vulnerability.
Garoon 5.10.0 or later
- 1. Back up the current Garoon installation and database.
- 2. Download the latest version of Cybozu Garoon (version 5.10.0 or later) from the official Cybozu portal.
- 3. Review the upgrade documentation for Garoon 5.10.x.
- 4. Execute the upgrade following the standard Garoon upgrade procedure.
- 5. Verify that the Garoon services start correctly after the upgrade.
- 6. Test that the file management functionality works as expected and confirm the vulnerability is resolved.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30602 — 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-2022-30602 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