dbcve.org
GaroonApplication · Cybozu

CVE-2013-6930

MEDIUM · 6.5 CVSS v2.0 Published 2014-01-29
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 page-navigation implementation in Cybozu Garoon 2.0.0 through 2.0.6, 2.1.0 through 2.1.3, 2.5.0 through 2.5.4, 3.0.0 through 3.0.3, 3.5.0 through 3.5.5, and 3.7.x before 3.7.3 allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors, a different vulnerability than CVE-2013-6929.

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 page-navigation implementation allows authenticated remote attackers to execute arbitrary SQL commands. The flaw affects versions 2.0.0 through 2.0.6, 2.1.0 through 2.1.3, 2.5.0 through 2.5.4, 3.0.0 through 3.0.3, 3.5.0 through 3.5.5, and 3.7.x before 3.7.3.

MitigationUpgrade Cybozu Garoon to version 3.7.3 or later to patch the SQL injection vulnerability in the page-navigation component.

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 installation
    Locate the Garoon installation directory or access the system information page through the administrative interface (typically /g/admin, /cgi-bin/cbgrn/env or the 'System Settings' menu). Look for the version information displayed in the product header or about section.
    Affected if Cybozu Garoon software is present in the environment
  2. Determine installed Garoon version
    Check the displayed version number from the system information page or examine the 'grn_version' file in the installation directory if accessible. Compare this version against the affected ranges: 2.0.0-2.0.6, 2.1.0-2.1.3, 2.5.0-2.5.4, 3.0.0-3.0.3, 3.5.0-3.5.5, and 3.7.x before 3.7.3.
    Affected if The installed version falls within any of the listed vulnerable version ranges
  3. Verify page-navigation component is accessible
    Confirm the page-navigation module is enabled by attempting to access the navigation feature through the web interface (typically accessed via portal or menu navigation). The vulnerability exists specifically in the page-navigation implementation.
    Affected if The page-navigation component is active and reachable via the web interface
  4. Check authentication configuration
    Review the authentication settings in Garoon's system administration to confirm user authentication is enabled. The vulnerability requires an authenticated attacker, so verify whether external or weak authentication is configured that could allow unauthorized access.
    Affected if User authentication is enabled and the application is accessible to authenticated users (including low-privilege users)
  5. Review access logs for suspicious SQL patterns
    Examine web server or Garoon access logs for unusual SQL syntax or database query patterns in page-navigation requests, such as UNION SELECT, OR 1=1, or other SQL injection payloads in URL parameters.
    Affected if Logs show SQL injection attempts targeting the page-navigation feature

The environment is affected if Cybozu Garoon is installed and the version falls within 2.0.0-2.0.6, 2.1.0-2.1.3, 2.5.0-2.5.4, 3.0.0-3.0.3, 3.5.0-3.5.5, or 3.7.x before 3.7.3, with page-navigation accessible to authenticated users.

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

Upgrade Cybozu Garoon to version 3.7.3 or later to patch the SQL injection vulnerability in the page-navigation component.

Fix this in Garoon Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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