Owncloud Desktop ClientApplication · Owncloud
CVE-2016-7102
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 Desktop before 2.2.3 allows local users to execute arbitrary code and possibly gain privileges via a Trojan library in a "special path" in the C: drive.
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 Desktop client versions before 2.2.3 are vulnerable to DLL hijacking. The application loads libraries from a 'special path' on the C: drive that local users can write to, allowing placement of a malicious DLL (Trojan library) that gets loaded with elevated privileges, enabling arbitrary code execution.
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
Owncloud Desktop ClientApplication
<= 2.2.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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 ownCloud Desktop client installationCheck for ownCloud Desktop client by looking in Program Files or Program Files (x86) for the ownCloud folder, or check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for ownCloud entriesAffected if ownCloud Desktop client is installed and running on the system
-
Determine installed versionOpen the ownCloud application, go to Help > About, or check the version in the Windows registry under the uninstall key for ownCloud, or right-click the ownCloud.exe file in Explorer and view Properties > DetailsAffected if The version number displayed is 2.2.2 or lower (any version before 2.2.3)
-
Identify DLL search path used by the applicationUse Sysinternals Process Monitor or Process Explorer to monitor the ownCloud client process for DLL loading activity, looking for LoadLibrary calls that reference paths on the C: driveAffected if The application loads DLLs from a writable directory accessible to local users
-
Check path writability for low-privilege usersUsing icacls or accesschk, examine the ACLs on the identified DLL search path directory to determine if standard users (non-admin) have Write or CreateFile permissionsAffected if Local non-admin users have Write permission to the directory from which ownCloud loads DLLs
-
Verify if ownCloud runs with elevated privilegesOpen Task Manager, find the ownCloud.exe process, right-click and select 'Run as administrator' to check if it requires elevation, or view the process properties in Process Explorer to check the integrity levelAffected if The ownCloud client process runs with elevated privileges (as administrator or with SYSTEM integrity) while loading DLLs from a user-writable path
You are affected if ownCloud Desktop client version 2.2.2 or earlier is installed and the application loads DLLs from a directory where local non-admin users have write permissions while the process runs elevated.
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 ownCloud Desktop client to version 2.2.3 or later. If immediate patching is not possible, restrict write permissions to the application's library search path directories to prevent unauthorized DLL placement.
Fix this in Owncloud Desktop Client
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-7102 — 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-7102 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