dbcve.org
GaroonApplication · Cybozu

CVE-2019-5945

CRITICAL · 9.8 CVSS v3.0 Published 2019-05-17
Fix available
A fix is available. Upgrade to after 4.10.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Cybozu Garoon 4.2.4 to 4.10.1 allow remote attackers to obtain the users' credential information via the authentication of Cybozu Garoon.

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

Cybozu Garoon versions 4.2.4 through 4.10.1 contain an authentication flaw that allows remote unauthenticated attackers to intercept or obtain user credential information. The vulnerability is network-exploitable with no user interaction required, earning the critical CVSS 9.8 rating.

MitigationApply the vendor-supplied patch (upgrade to version 4.10.2 or later). Until patched, restrict network access to Garoon servers to trusted IP ranges and monitor for unauthorized access attempts.

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.2.4, <= 4.10.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
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checks

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

  1. Identify Cybozu Garoon installation
    Check if Cybozu Garoon is installed on the system by looking for Garoon-related processes, services, or the presence of the application directory. Garoon typically runs as a web application on an application server.
    Affected if Cybozu Garoon software is found on the system
  2. Locate the installed version number
    Access the Garoon system information page via the administrative interface, typically found under System Settings > System Information, or check the version information file in the Garoon installation directory.
    Affected if The version cannot be determined or the software is present but version info is inaccessible
  3. Compare version against affected range
    If the version is found, compare it to the affected range: versions 4.2.4 through 4.10.1 are vulnerable. Any version within this inclusive range means the environment is affected.
    Affected if The installed version is >= 4.2.4 and <= 4.10.1
  4. Check network exposure of Garoon web interface
    Determine if the Garoon web portal is accessible from untrusted networks by testing external connectivity to the Garoon HTTP/HTTPS ports from outside the internal network.
    Affected if Garoon is exposed to the public internet or untrusted networks

The environment is affected if Cybozu Garoon is installed and the running version falls between 4.2.4 and 4.10.1 inclusive, especially when the interface is network-accessible.

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 4.10.1
Interim mitigation

Apply the vendor-supplied patch (upgrade to version 4.10.2 or later). Until patched, restrict network access to Garoon servers to trusted IP ranges and monitor for unauthorized access attempts.

Recommended fix Moderate confidence

Garoon 4.10.2 or later (or latest stable 5.x release)

  1. 1. Review the current Garoon installation to confirm the exact version running (can be checked in Garoon administrator settings > System Administration > System Settings > Product Information)
  2. 2. Plan for an upgrade during a scheduled maintenance window
  3. 3. Back up the current Garoon database and configuration files before proceeding with the upgrade
  4. 4. Upgrade Garoon to the latest version available from Cybozu (version 4.10.2 or later, or the latest 5.x release)
  5. 5. After upgrade, verify that the Garoon service starts successfully
  6. 6. Log in as an administrator and confirm all users can authenticate properly
  7. 7. Review system logs for any unusual authentication attempts
Caveat Review Cybozu release notes for any configuration or compatibility changes between 4.x and 5.x versions before upgrading across major versions

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

Fix this in Garoon Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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