CVE-2017-2256
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 · uneditedCross-site scripting vulnerability in Cybozu Garoon 3.0.0 to 4.2.5 allows an attacker to inject arbitrary web script or HTML via "Rich text" function of the application "Memo".
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.0.0 through 4.2.5 contains a stored cross-site scripting (XSS) vulnerability in the Memo application's 'Rich text' function. Attackers can inject malicious HTML or JavaScript code that executes when other users view the crafted memo, potentially stealing session cookies or performing actions on behalf of authenticated users.
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.0.0= 3.0.1= 3.0.2= 3.0.3= 3.1.0= 3.1.1= 3.1.2= 3.1.3= 3.5.0= 3.5.1= 3.5.2= 3.5.3CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 or access the application's login page. Garoon is typically installed on Windows servers or Linux systems and accessed via web browser at a configured URL.Affected if Cybozu Garoon software is present in the environment
-
Identify installed Garoon versionAccess the Garoon administrator menu, typically found under 'System Settings' or 'System Administration'. Look for version information displayed in the system configuration or about page. Alternatively, check installation files or system registry if accessible.Affected if The installed version matches 3.0.0 through 4.2.5, or specifically matches any of these versions: 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.5.0, 3.5.1, 3.5.2, 3.5.3
-
Verify Memo application is enabledIn the Garoon administrator console, navigate to 'Application Settings' or 'System Applications' and confirm whether the Memo application module is installed and active for users.Affected if The Memo application is enabled and accessible to users in the environment
-
Confirm Rich text function is active in MemoIn the Memo application settings accessible through the administrator console, check whether the Rich text editor feature is turned on. This is often found under Memo application configuration or user settings.Affected if The Rich text function is enabled in the Memo application settings
The environment is affected if Cybozu Garoon versions 3.0.0 through 4.2.5 is installed, the Memo application is enabled, and the Rich text function is turned on, allowing stored XSS attacks via crafted memos.
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 to Cybozu Garoon version 4.2.6 or later, which contains the security patch. If immediate upgrade is not possible, consider disabling the Rich text function in the Memo application or implementing Web Application Firewall (WAF) rules to filter malicious input.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2256 — 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-2017-2256 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