CVE-2015-8484
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 · uneditedCybozu Office 9.9.0 through 10.3.0 allows remote authenticated users to bypass intended calendar-viewing restrictions via unspecified vectors, a different vulnerability than CVE-2015-8485, CVE-2015-8486, and CVE-2016-1152.
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 Office 9.9.0 through 10.3.0 contains an access control bypass vulnerability in its calendar functionality that allows authenticated users to view calendar entries they should not have permission to access. This is an authorization flaw rather than an authentication bypass.
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
- Low
- Integrity
- None
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L
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 Office versionAccess the system administration panel or check the product version information typically found in the About section of Cybozu Office. The version number is displayed in the system information or license details.Affected if The installed version is any of these: 9.9.0, 10.0.0, 10.0.1, 10.0.2, 10.1.0, 10.1.2, 10.0.2, or 10.3.0.
-
Confirm calendar module is activeVerify that the calendar application module is enabled for users in the Cybozu Office system. Check the application settings or user access controls to confirm calendar functionality is available.Affected if The calendar module is enabled and users have access to create or view calendar entries.
-
Review calendar sharing permissionsExamine the calendar sharing settings to determine if any entries are configured with permissions that restrict access to specific users or groups. Look for shared calendars where permission settings may not be properly enforced.Affected if Calendar entries exist with restricted permissions (such as private or group-limited entries) and users outside those permissions may still be able to view them.
-
Test cross-user calendar accessCreate two test users with different calendar permission levels. Have User A create a private calendar entry, then attempt to access it from User B's account who should not have permission to view those entries.Affected if User B can view User A's private or restricted calendar entries despite not being granted permission.
You are affected if Cybozu Office version 9.9.0 through 10.3.0 is installed AND the calendar module is enabled, allowing unauthorized users to view restricted calendar entries.
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 fix for this calendar viewing restriction bypass. If immediate patching is not possible, review and restrict user calendar permissions as a compensating control.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-8484 — 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-8484 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