OwncloudApplication

CVE-2021-35946

CRITICAL · 9.8 CVSS v3.1 Published 2021-09-07
Fix available
A fix is available. Upgrade to 10.8.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
A receiver of a federated share with access to the database with ownCloud version before 10.8 could update the permissions and therefore elevate their own permissions.

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

A privilege escalation vulnerability in ownCloud versions before 10.8 allows a receiver of a federated share who has direct database access to modify share permissions in the database, thereby elevating their own permissions beyond what the federated share should grant.

MitigationUpgrade ownCloud to version 10.8 or later which includes proper server-side permission validation for federated shares.

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:< 10.8.0

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 checks

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

  1. Identify ownCloud version
    Check the ownCloud version by accessing the ownCloud admin panel or checking the version file in the ownCloud installation directory (e.g., looking at version.php or the oc_appconfig table in the database)
    Affected if The installed version is below 10.8.0 (e.g., 10.7.0, 10.6.0, etc.)
  2. Confirm federated sharing is enabled
    Check if the Federated Sharing app is enabled in ownCloud by reviewing the app list in the admin panel or querying the oc_appconfig table for 'federation' related settings
    Affected if Federated sharing is enabled and users can receive or send federated shares
  3. Verify database access controls
    Review database user permissions and access controls to determine if regular users or potential attackers could have direct database access to the ownCloud database
    Affected if Any user with federated share receipt capability also has direct database access or the database is accessible beyond the application layer

The environment is affected if ownCloud version is before 10.8.0 AND federated sharing is enabled AND users who receive federated shares could potentially have database access.

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.

dbcve · scoped
Upgrade available Upgrade to 10.8.0 or later
Fixed in 10.8.0
Interim mitigation

Upgrade ownCloud to version 10.8 or later which includes proper server-side permission validation for federated shares.

Recommended fix High confidence

ownCloud 10.8.0 or later

  1. 1. Create a complete backup of the ownCloud data directory, database, and configuration files
  2. 2. Download ownCloud 10.8.0 or later from the official ownCloud download server
  3. 3. Extract the new ownCloud package to a temporary location
  4. 4. Replace the existing ownCloud installation files with the new version, preserving the config directory
  5. 5. Run the ownCloud upgrade command: occ upgrade (from the ownCloud directory)
  6. 6. Clear any caching mechanisms (redis, memcached) if used
  7. 7. Verify the upgrade was successful by logging in and checking the ownCloud version in the admin panel
  8. 8. Test federated share functionality to confirm the fix is working
Caveat Review ownCloud 10.8.0 release notes for any changes to apps or features you rely on before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Owncloud Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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