dbcve.org
OwncloudApplication

CVE-2014-3836

MEDIUM · 6.8 CVSS v2.0 Published 2014-06-04
Fix available
A fix is available. Upgrade to after 6.0.2 or later.
See remediation →
77/100
Remediation priority · High
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
Multiple cross-site request forgery (CSRF) vulnerabilities in ownCloud Server before 6.0.3 allow remote attackers to hijack the authentication of users for requests that (1) conduct cross-site scripting (XSS) attacks, (2) modify files, or (3) 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 confidence

Multiple CSRF vulnerabilities in ownCloud Server before version 6.0.3 allow remote attackers to hijack authenticated user sessions to perform cross-site scripting attacks, modify files, or rename files through malicious requests.

MitigationUpgrade ownCloud Server to version 6.0.3 or later to address the CSRF vulnerabilities.

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:<= 6.0.2
Owncloud ServerApplication
Affected:= 6.0.0= 6.0.1

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/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 checks

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

  1. Check ownCloud Server version via admin interface
    Log in to ownCloud with an administrator account and navigate to the admin settings page to view the installed version number
    Affected if The displayed version is 6.0.0, 6.0.1, or any version up to 6.0.2
  2. Check ownCloud version via config file
    If you have filesystem access, locate the ownCloud version file (typically version.php or similar config file in the ownCloud root directory) and read the version string
    Affected if The version string matches 6.0.0, 6.0.1, or 6.0.2
  3. Compare version against affected ranges
    Verify your installed version falls within the affected ranges: exactly 6.0.0, exactly 6.0.1, or any version <= 6.0.2
    Affected if Your version is within these ranges (6.0.0 through 6.0.2 inclusive)

You are affected if your ownCloud Server installation is version 6.0.0, 6.0.1, or any version up to and including 6.0.2, as these versions contain the CSRF vulnerabilities described in CVE-2014-3836

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 6.0.2
Interim mitigation

Upgrade ownCloud Server to version 6.0.3 or later to address the CSRF vulnerabilities.

Fix this in Owncloud Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-3836 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-3836 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