CVE-2015-8489
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 · uneditedcustomapp in Cybozu Office 9.9.0 through 10.3.0 allows remote authenticated users to cause a denial of service (excessive database locking) via a crafted CSV file, a different vulnerability than CVE-2016-1153.
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 confidenceCybozu Office versions 9.9.0 through 10.3.0 contain a denial of service vulnerability in the customapp component. Authenticated users can upload a crafted CSV file that triggers excessive database locking, rendering the application unavailable. The vulnerability requires authentication but no elevated privileges.
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= 9.9.0= 10.0.0= 10.0.1= 10.0.2= 10.1.0= 10.1.2= 10.2.0= 10.3.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Cybozu Office versionAccess the system administration panel or check the product information within Cybozu Office. Look for the version number displayed in the About or System Information section.Affected if The installed version matches any of: 9.9.0, 10.0.0, 10.0.1, 10.0.2, 10.1.0, 10.1.2, 10.2.0, or 10.3.0
-
Confirm the customapp component is configuredNavigate to the customapp settings within Cybozu Office administration. Check if any custom applications are created or if the customapp module is enabled.Affected if Custom applications exist or the customapp component is enabled in the environment
-
Verify CSV import is accessible to authenticated usersCheck the permissions settings for the customapp module. Determine whether standard authenticated users have the ability to import CSV files into custom applications.Affected if Authenticated users without elevated privileges can import CSV files into custom applications
-
Check for database locking symptomsReview database connection logs or application logs for indications of prolonged database locks, slow queries, or application unresponsiveness occurring after CSV imports.Affected if Database locking issues or denial of service symptoms are observed following CSV imports in the customapp module
You are affected if Cybozu Office is version 9.9.0 through 10.3.0 AND the customapp component with CSV import capability is accessible to authenticated users.
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 dataUpgrade Cybozu Office to version 10.4.0 or later, which contains the patch for this vulnerability. As a compensating control, consider restricting CSV import functionality to trusted users until the upgrade is applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2015-8489 — 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-2015-8489 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