CVE-2021-35946
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 · uneditedA 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 confidenceA 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.
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< 10.8.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify ownCloud versionCheck 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.)
-
Confirm federated sharing is enabledCheck 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 settingsAffected if Federated sharing is enabled and users can receive or send federated shares
-
Verify database access controlsReview database user permissions and access controls to determine if regular users or potential attackers could have direct database access to the ownCloud databaseAffected 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.
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 · scoped10.8.0
Upgrade ownCloud to version 10.8 or later which includes proper server-side permission validation for federated shares.
ownCloud 10.8.0 or later
- 1. Create a complete backup of the ownCloud data directory, database, and configuration files
- 2. Download ownCloud 10.8.0 or later from the official ownCloud download server
- 3. Extract the new ownCloud package to a temporary location
- 4. Replace the existing ownCloud installation files with the new version, preserving the config directory
- 5. Run the ownCloud upgrade command: occ upgrade (from the ownCloud directory)
- 6. Clear any caching mechanisms (redis, memcached) if used
- 7. Verify the upgrade was successful by logging in and checking the ownCloud version in the admin panel
- 8. Test federated share functionality to confirm the fix is working
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-35946 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