CVE-2017-2114
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 Office 10.0.0 to 10.5.0 allows remote authenticated attackers to inject arbitrary web script or HTML 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 confidenceCross-site scripting (XSS) vulnerability in Cybozu Office versions 10.0.0 through 10.5.0 allows remote authenticated attackers to inject arbitrary web script or HTML via unspecified vectors. The medium CVSS score reflects the need for authentication and potential impact on other users viewing injected content.
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= 10.1.0= 10.1.2= 10.2.0= 10.3.0= 10.4.0= 10.5.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
- 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.
-
Identify Cybozu Office installationCheck for Cybozu Office by looking for its installation directory, service, or by accessing the web application's login page. Common paths include C:\Program Files\Cybozu or /opt/cybozu on Linux systems.Affected if Cybozu Office is found running in the environment
-
Determine installed versionLocate the version information in the product's about page, system settings, or check version files in the installation directory. The version is typically displayed in the header or footer of the web interface, or in a version.txt file within the installation folder.Affected if The installed version matches 10.1.0, 10.1.2, 10.2.0, 10.3.0, 10.4.0, or 10.5.0, or falls within the 10.0.0 through 10.5.0 range
-
Verify XSS input vectors are accessibleConfirm that user-accessible features exist in Cybozu Office where authenticated users can submit content, such as bulletin boards, calendars, address books, or message boards. These represent potential vectors for XSS injection.Affected if User submission features are enabled and accessible to authenticated users
-
Review application logs for XSS indicatorsExamine Cybozu Office server logs, web server logs, and security audit logs for unusual script tags, HTML elements, or encoded payloads that may indicate exploitation attempts or successful XSS injections.Affected if Logs contain suspicious script or HTML injection patterns in user-submitted content fields
The environment is affected if Cybozu Office version 10.0.0 through 10.5.0 is installed and user-authenticated features are accessible, as the XSS vulnerability can be exploited by any authenticated user injecting malicious scripts into unspecified input fields.
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 for CVE-2017-2114 to upgrade Cybozu Office beyond version 10.5.0. Additionally, implement output encoding and input validation as defense-in-depth measures for user-supplied content.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2114 — 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-2114 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