CVE-2013-6002
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 · uneditedThe server in Cybozu Garoon before 3.7 SP1 allows remote attackers to cause a denial of service (CPU consumption) 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 confidenceCybozu Garoon versions prior to 3.7 SP1 contain a denial of service vulnerability that allows remote attackers to exhaust server CPU resources by sending specially crafted requests with unspecified vectors, causing the application to become unresponsive.
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<= 3.7= 2.0= 2.1= 2.5= 3.0= 3.1= 3.5CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cybozu Garoon installationLocate Cybozu Garoon installation directory or check system services for 'garoon' process/service. Common installation paths include C:\Program Files\Cybozu or /opt/cybozu/ on Linux systems.Affected if Cybozu Garoon software is found running on the system
-
Determine installed Garoon versionAccess the Garoon system information page (typically /garoon/portal/ or through the administration panel) or check version files in the installation directory for a version.txt or similar file.Affected if The installed version cannot be determined or is found within the affected list
-
Compare version against affected rangesReview the identified version against the affected versions: 2.0, 2.1, 2.5, 3.0, 3.1, 3.5, or any version 3.7 or lower.Affected if The installed version matches 2.0, 2.1, 2.5, 3.0, 3.1, 3.5, or is 3.7 or lower (prior to SP1)
-
Verify network exposureCheck if the Garoon web interface is exposed to network access by reviewing firewall rules or web server configuration for port 80/443 or custom Garoon ports.Affected if Garoon is accessible from network locations beyond localhost
A system is affected if Cybozu Garoon version 2.0, 2.1, 2.5, 3.0, 3.1, 3.5, or any version 3.7 or lower is installed and the application is network-accessible.
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.
From vendor dataApply the vendor patch by upgrading to Cybozu Garoon 3.7 SP1 or later version to resolve the CPU consumption vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6002 — 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-2013-6002 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