Owncloud ClientApplication · Owncloud
CVE-2022-25339
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 · uneditedownCloud owncloud/android 2.20 has Incorrect Access Control for local attackers.
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 · moderate confidenceThe ownCloud Android app version 2.20 contains an Incorrect Access Control vulnerability that allows local attackers to access sensitive data or functionality without proper authorization. This is a local privilege escalation issue where the app fails to properly validate access permissions, potentially exposing user data stored on the device to unauthorized local access.
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
Owncloud ClientApplication
< 2.20.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the ownCloud Android app on the deviceNavigate to Settings > Apps on the Android device and locate the ownCloud application entry. The app may be labeled as 'ownCloud' or 'ownCloud Files' in the app list.Affected if The ownCloud Android app is installed on the device
-
Determine the installed version numberTap on the ownCloud app entry in Settings > Apps, then look for 'Version' or 'Version info' in the app details screen. Alternatively, use ADB command: adb shell dumpsys package com.owncloud.android | grep versionNameAffected if Unable to determine the version number
-
Compare installed version against affected rangeCheck if the installed version is lower than 2.20.0. The affected versions are any version string that numerically or lexically precedes 2.20.0 (e.g., 2.19.x, 2.18.x, 2.10.0, 1.9.0, etc.)Affected if Installed version is < 2.20.0
If the ownCloud Android app is installed at a version lower than 2.20.0, the device is affected by this local privilege escalation vulnerability.
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 · scoped2.20.0
Users should upgrade to a patched version of the ownCloud Android app. Since this is a local access control issue, ensure devices are not shared with untrusted users and avoid installing the app on compromised devices.
ownCloud Android client version 2.20.0
- Update the ownCloud Android application from Google Play Store or F-Droid to version 2.20.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Owncloud Client
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2022-25339 — 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-2022-25339 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