GaroonApplication · Cybozu

CVE-2014-0821

MEDIUM · 6.5 CVSS v2.0 Published 2014-02-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
SQL injection vulnerability in the download feature in Cybozu Garoon 2.x through 2.5.4 and 3.x through 3.7 SP3 allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors, a different vulnerability than CVE-2013-6930 and CVE-2013-6931.

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

SQL injection vulnerability in Cybozu Garoon's download feature allows remote authenticated users to execute arbitrary SQL commands via unsanitized input. The flaw affects versions 2.x through 2.5.4 and 3.x through 3.7 SP3. This is a classic SQL injection where user-controlled data in the download function is not properly parameterized before being used in database queries.

MitigationApply vendor patches for Cybozu Garoon to the latest supported version (beyond 3.7 SP3). If immediate patching is not feasible, restrict network access to the Garoon application to trusted users only and implement WAF rules to detect SQL injection patterns in requests.

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:= 2.0= 2.0.0= 2.0.1= 2.0.2= 2.0.3= 2.0.4= 2.0.5= 2.0.6= 2.1= 2.1.0= 2.1.1= 2.1.2

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
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

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

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 installed version
    Access the Garoon administration panel and navigate to System Settings > System Information, or inspect the version file typically located in the Garoon installation directory (such as version.ini or a config file in the base installation folder).
    Affected if The installed version falls within 2.x through 2.5.4, or 3.x through 3.7 SP3.
  2. Verify download module is accessible
    Confirm that the download feature (typically accessed via the /download/ endpoint or file attachment download functionality) is enabled in the Garoon system settings and accessible to users.
    Affected if The download module is enabled and accessible to authenticated users.
  3. Check authentication configuration
    Review Garoon's authentication settings in the administration panel to determine if remote user authentication is enabled (allowing external users to log in to the system).
    Affected if Remote authenticated users can access the Garoon application.
  4. Inspect download request parameters
    Use a web proxy or browser developer tools to capture a download request (such as downloading an attachment or file). Examine the request parameters to see if user-controlled input is passed directly to the server without obvious parameterization.
    Affected if The download function passes user-supplied input (such as file IDs, IDs, or other parameters) directly into SQL queries without proper sanitization or prepared statements.

A system is affected if it runs Cybozu Garoon version 2.x through 2.5.4 or 3.x through 3.7 SP3, has the download feature enabled, and allows remote authenticated users to access the application.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for Cybozu Garoon to the latest supported version (beyond 3.7 SP3). If immediate patching is not feasible, restrict network access to the Garoon application to trusted users only and implement WAF rules to detect SQL injection patterns in requests.

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-0821 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-0821 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