OwncloudApplication

CVE-2014-9048

MEDIUM · 5.0 CVSS v2.0 Published 2015-02-04
Fix available
A fix is available. Upgrade to after 5.0.17 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The documents application in ownCloud Server 6.x before 6.0.6 and 7.x before 7.0.3 allows remote attackers to bypass the password-protection for shared files via the API.

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 confidence

The documents application in ownCloud Server 6.x before 6.0.6 and 7.x before 7.0.3 fails to properly enforce password protection when accessing shared files through the API, allowing remote attackers to bypass authentication and access password-protected shared documents.

MitigationUpgrade ownCloud Server to version 6.0.6 or 7.0.3 or later, which contain the fix for proper password validation on shared file access via the API.

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
Affected:<= 5.0.17
Owncloud ServerApplication
Affected:= 5.0.0= 5.0.1= 5.0.2= 5.0.3= 5.0.4= 5.0.5= 5.0.6= 5.0.7= 5.0.8= 5.0.9= 5.0.10= 5.0.11

CVSS 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
None
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:N/I:P/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed ownCloud Server version
    Access the ownCloud admin panel and navigate to the server info page, or check the version file in the ownCloud installation directory (version.php or similar). Compare against the affected versions: 5.0.0 through 5.0.11 or any version <= 5.0.17.
    Affected if The installed version is 5.0.0 through 5.0.11, or is <= 5.0.17 (for the Owncloud product line listed). Note: The summary also mentions 6.x before 6.0.6 and 7.x before 7.0.3 as affected.
  2. Verify the documents application is enabled
    Log in as an admin, go to the Apps section, and check if the 'Documents' application is installed and enabled.
    Affected if The Documents application is enabled. The vulnerability only affects environments using the documents app.
  3. Identify password-protected shared documents
    Check existing shares via the ownCloud web interface or database for shared files with password protection enabled.
    Affected if There are shared documents configured with password protection. The vulnerability allows bypassing this protection via API.
  4. Test API access to password-protected shares
    Use a web request tool (curl) to access a password-protected shared document via the ownCloud API endpoint (typically /remote.php/webdav/ or the documents API) without providing authentication credentials.
    Affected if The API returns the document content without requiring password authentication. This confirms the vulnerability is present.

You are affected if your ownCloud Server version is within the vulnerable range (5.0.x as listed, or 6.x < 6.0.6 or 7.x < 7.0.3 per the summary), the Documents application is enabled, and password-protected shared documents exist that can be accessed via API without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 5.0.17
Interim mitigation

Upgrade ownCloud Server to version 6.0.6 or 7.0.3 or later, which contain the fix for proper password validation on shared file access via the API.

Fix this in Owncloud Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-9048 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-9048 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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