CVE-2016-1190
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 Garoon 3.1 through 4.2 allows remote authenticated users to bypass intended restrictions on MultiReport reading 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 3.1 through 4.2 contain an access control bypass where authenticated users can read MultiReport entries that should be restricted from their access level. This is an authorization flaw in the MultiReport module allowing privilege escalation through unspecified vectors.
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.1.0= 3.1.1= 3.1.2= 3.1.3= 3.5.0= 3.5.1= 3.5.2= 3.5.3= 3.5.4= 3.5.5= 3.7.0= 3.7.1CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Confirm Cybozu Garoon installationLocate the Garoon installation directory (commonly C:\Program Files\Cybozu or /var/www/garoon) or check running services for garoon or cbgrn processesAffected if Cybozu Garoon software is present on the system
-
Identify installed Garoon versionCheck the version information in the Garoon installation: look for a version file (often version.txt or similar) in the install directory, or access Garoon system information via the administrative interface under 'System Settings' > 'System Information'Affected if The installed version matches 3.1.0 through 4.2 (including specific point releases like 3.1.1, 3.5.0, 3.7.1, etc.)
-
Verify MultiReport module is enabledLog into Garoon as an administrator and navigate to 'System Settings' > 'Application Settings' > 'MultiReport' to confirm the module is active, or check the cbgrn.ini or similar configuration file for MultiReport enabled statusAffected if The MultiReport module is installed and enabled in the Garoon application settings
-
Check for restricted MultiReport reportsIn the Garoon administrative interface, go to 'MultiReport' > 'Report List' and review reports to identify any that have restricted access permissions configured (reports set to limited user groups or roles)Affected if There exist MultiReport reports with access restrictions configured, as unrestricted reports would not expose the authorization flaw
You are affected if Cybozu Garoon version 3.1.0 through 4.2 is installed, the MultiReport module is enabled, and there are MultiReport entries with restricted access permissions that could be accessed by lower-privileged 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 dataApply the vendor patch from Cybozu (refer to JVN#16258492 for specific patch/upgrade path). If immediate patching is not possible, review and restrict user role assignments for the MultiReport module as a compensating control.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1190 — 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-2016-1190 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