dbcve.org
OwncloudApplication

CVE-2013-0299

MEDIUM · 6.8 CVSS v2.0 Published 2014-03-14
Fix available
A fix is available. Upgrade to after 4.0.11 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 before 4.0.12 and 4.5.x before 4.5.7 allow remote attackers to hijack the authentication of users for requests that (1) change the timezone for the user via the lat and lng parameters to apps/calendar/ajax/settings/guesstimezone.php, (2) disable or enable the automatic timezone detection via the timezonedetection parameter to apps/calendar/ajax/settings/timezonedetection.php, (3) import user accounts via the admin_export parameter to apps/admin_migrate/settings.php, (4) overwrite user files via the operation parameter to apps/user_migrate/ajax/export.php, or (5) change the authentication server URL via unspecified vectors to apps/user_ldap/settings.php.

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 cross-site request forgery (CSRF) vulnerabilities in ownCloud versions before 4.0.12 and 4.5.7 allow remote attackers to hijack authenticated user sessions. The vulnerabilities exist in five distinct endpoints handling sensitive operations: timezone settings, timezone detection toggle, user account imports, user file exports/overwrites, and LDAP authentication server configuration.

MitigationUpgrade ownCloud to version 4.0.12 or 4.5.7 or later to obtain patched versions. Alternatively, implement anti-CSRF tokens (synchronizer token pattern) on all state-changing endpoints.

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:<= 4.0.11
Owncloud ServerApplication
Affected:= 3.0.0= 3.0.1= 3.0.2= 3.0.3= 4.0.0= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7

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. Identify ownCloud version
    Locate the ownCloud version file (typically version.php in the root directory or check the admin panel for version information)
    Affected if Installed version is 4.0.11 or earlier, OR version is exactly 3.0.0, 3.0.1, 3.0.2, 3.0.3, 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6, or 4.0.7
  2. Verify timezone settings endpoint exposure
    Access the personal settings page and locate timezone configuration options under date/time preferences
    Affected if Timezone settings are available and no anti-CSRF token is submitted with timezone change requests
  3. Check user import functionality
    Navigate to the admin or user management panel and locate any user import feature (CSV or LDAP import)
    Affected if User import functionality exists without CSRF token validation on the import action
  4. Examine file export/overwrite capability
    Test the file download/export functionality, particularly trying to overwrite existing files via export endpoints
    Affected if File export endpoints lack CSRF token protection for overwrite operations
  5. Inspect LDAP server configuration interface
    Access the LDAP configuration settings panel (typically under Admin > LDAP)
    Affected if LDAP server configuration can be modified without requiring anti-CSRF token submission

The environment is affected if ownCloud version is within the vulnerable range (4.0.11 or earlier, or matching the specific 3.0.x/4.0.x versions listed) AND the sensitive endpoints lack anti-CSRF token protection.

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

Upgrade ownCloud to version 4.0.12 or 4.5.7 or later to obtain patched versions. Alternatively, implement anti-CSRF tokens (synchronizer token pattern) on all state-changing endpoints.

Fix this in Owncloud Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,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 $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0299 — 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-2013-0299 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