dbcve.org
GaroonApplication · Cybozu

CVE-2014-1987

HIGH · 10.0 CVSS v2.0 Published 2014-07-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The CGI component in Cybozu Garoon 3.1.0 through 3.7 SP3 allows remote attackers to execute arbitrary commands via unspecified vectors.

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

Command injection vulnerability in the CGI component of Cybozu Garoon allows remote attackers to execute arbitrary OS commands. Affects versions 3.1.0 through 3.7 SP3. The attack vector and specific vulnerable parameters are not detailed in the available description.

MitigationApply the vendor-supplied patch for Cybozu Garoon to upgrade beyond version 3.7 SP3, or implement network-level restrictions to limit CGI exposure to trusted networks only.

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:= 3.1.0= 3.1.1= 3.1.2= 3.1.3= 3.5.0= 3.5.1= 3.5.2= 3.5.3= 3.5.4= 3.5.5= 3.7

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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. Verify Cybozu Garoon is installed
    Check for Garoon installation directories or look for garoon-related processes and services running on the server. Common locations include /opt/cybozu/ or C:\Program Files\cybozu\ on Windows.
    Affected if Cybozu Garoon software is found on the system
  2. Identify installed Garoon version
    Locate and read the version information file, typically found in the Garoon installation directory or accessible via the administrative web interface under system information.
    Affected if The version is 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.5.0 through 3.5.5, or 3.7 through 3.7 SP3
  3. Confirm CGI component is enabled
    Check the Garoon configuration or web server settings to determine if the CGI module is active. Look for cgi.exe, cgibin, or similar CGI executables in the Garoon web directory.
    Affected if CGI component is enabled and accessible via HTTP/HTTPS
  4. Assess network accessibility of CGI endpoint
    Test if the Garoon CGI endpoint is reachable from network locations by attempting HTTP/HTTPS requests to typical CGI paths such as /cgi-bin/garoon/ or /garoon/cg.exe
    Affected if The CGI interface is exposed to untrusted networks without firewall restrictions

A system is affected if it runs any Cybozu Garoon version from 3.1.0 to 3.7 SP3 with the CGI component enabled and accessible over the network.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patch for Cybozu Garoon to upgrade beyond version 3.7 SP3, or implement network-level restrictions to limit CGI exposure to trusted networks only.

Recommended fix Moderate confidence

Latest stable release of Garoon (contact Cybozu support for specific version as 3.7 SP3+ contains the fix)

  1. 1. Identify the current Garoon version by accessing the administrative interface or checking system documentation.
  2. 2. Access the Cybozu support portal or official download page to obtain the latest stable version of Garoon.
  3. 3. Review the Garoon upgrade documentation for your specific version path.
  4. 4. Create a complete backup of the current Garoon installation including database and configuration files.
  5. 5. Test the upgrade in a staging environment before applying to production.
  6. 6. Execute the upgrade following Cybozu's official upgrade procedure.
  7. 7. Verify the CGI component is functioning correctly after upgrade.
  8. 8. Confirm the vulnerability is resolved by checking the version information.
Caveat Upgrade may require database migration; test thoroughly in non-production environment first

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 / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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