OwncloudApplication
CVE-2017-8896
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 · uneditedownCloud Server before 8.2.12, 9.0.x before 9.0.10, 9.1.x before 9.1.6, and 10.0.x before 10.0.2 are vulnerable to XSS on error pages by injecting code in url parameters.
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 confidenceownCloud Server contains a reflected cross-site scripting (XSS) vulnerability where malicious script code can be injected via URL parameters and executed on error pages. This affects multiple version branches (8.2.x, 9.0.x, 9.1.x, and 10.0.x) prior to their respective patched releases.
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
OwncloudApplication
<= 8.2.11>= 9.0.0, <= 9.0.9> 9.1.0, <= 9.1.5>= 10.0.0, < 10.0.2CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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 installed ownCloud versionLog into the ownCloud web interface as an administrator and navigate to the Admin page. The version number is displayed at the bottom of the left sidebar. Alternatively, check the version.php file in the ownCloud installation directory.Affected if The installed version falls within any of these ranges: 8.2.x through 8.2.11; 9.0.0 through 9.0.9; 9.1.1 through 9.1.5; or 10.0.0 through 10.0.1
-
Compare version against patched releasesNote the exact version number found in the previous step and compare it against the known safe versions: 8.2.12 or later, 9.0.10 or later, 9.1.6 or later, or 10.0.2 or later.Affected if The installed version is lower than any of these patched versions.
-
Confirm error page functionality is accessibleTrigger an error condition by requesting a non-existent page or invalid parameter, such as accessing https://your-owncloud-server/index.php/fakepagethatdoesnotexist or adding a malformed parameter like ?invalidparam=<script>testAffected if Error pages are displayed to users without sanitization of URL parameters, which can be verified by examining whether the URL parameter values appear reflected in the response.
You are affected if your installed ownCloud version is 8.2.11 or earlier, 9.0.9 or earlier, 9.1.5 or earlier, or between 10.0.0 and 10.0.1 inclusive.
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 data10.0.2
Upgrade ownCloud Server to version 8.2.12, 9.0.10, 9.1.6, or 10.0.2 or later to remediate the XSS vulnerability in error page URL parameter handling.
Fix this in Owncloud
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8896 — 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-8896 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