OwncloudApplication
CVE-2014-3834
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 6.0.3 does not properly check permissions, which allows remote authenticated users to (1) access the contacts of other users via the address book or (2) rename files 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 · high confidenceownCloud Server before 6.0.3 contains an improper authorization vulnerability where the application fails to properly validate user permissions. This allows any authenticated user to access other users' contacts through the address book feature and rename files they do not own or have permission to modify.
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
<= 6.0.2
Owncloud ServerApplication
= 6.0.0= 6.0.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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 versionLocate the ownCloud version file or check the administrative interface version display. Common locations include version.php in the root directory or the admin settings page.Affected if The installed version is 6.0.0, 6.0.1, or any version 6.0.2 or lower.
-
Verify address book application is activeAccess the ownCloud admin panel or check the apps directory to determine if the Contacts or Address Book app is installed and enabled for users.Affected if The address book/contacts application is enabled and accessible to authenticated users on an affected ownCloud version.
-
Confirm user authentication is enabledVerify that ownCloud user authentication is configured and functional, allowing users to log in to the system.Affected if User authentication is enabled and regular users can log in to the ownCloud instance.
-
Test contact access between usersCreate two test user accounts, log in as the first user and create a contact in the address book. Log in as the second user and attempt to access or view the first user's contacts through the address book feature.Affected if An authenticated user can view another user's contacts without proper authorization.
-
Test unauthorized file renamingAs one user, create a file or folder. As a different user without ownership or write permissions to that file, attempt to rename the file through the web interface or API.Affected if A user can rename files or folders they do not own or lack permission to modify.
The environment is affected if running ownCloud version 6.0.0, 6.0.1, or any version 6.0.2 or lower and the address book feature is enabled for 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 dataUpgrade ownCloud Server to version 6.0.3 or later which contains the proper permission validation fixes.
Fix this in Owncloud
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3834 — 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-2014-3834 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