dbcve.org
Owncloud ClientApplication · Owncloud

CVE-2022-25338

MEDIUM · 6.8 CVSS v3.1 Published 2022-04-07
Fix available
A fix is available. Upgrade to 2.20.0 or later.
See remediation →
73/100
Remediation priority · Elevated
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
ownCloud owncloud/android before 2.20 has Incorrect Access Control for physically proximate 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 confidence

The ownCloud Android mobile application (versions before 2.20) contains an incorrect access control vulnerability that allows physically proximate attackers to bypass authentication or authorization controls. This typically means someone with physical access to an unlocked or briefly unattended device can access sensitive data or functionality without proper credentials.

MitigationUpdate the ownCloud Android application to version 2.20 or later. Additionally, enforce strong device-level security measures including screen locks, encryption, and remote wipe capabilities to mitigate physical access attacks.

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
Affected:< 2.20.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
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/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. Verify ownCloud client is installed
    On the Android device, go to Settings > Apps and search for 'ownCloud' or 'ownCloud Files'. Confirm the application is present on the device.
    Affected if If the ownCloud client app is found on the device, proceed to version check.
  2. Determine installed version number
    Open the app listing in Google Play Store and view the 'Version' field, or go to Settings > Apps > ownCloud and check the version under 'App info'. Note the exact version number displayed.
    Affected if If no version number is displayed or the app is not found, the detection cannot be completed.
  3. Compare version to affected range
    Compare the installed version number to the vulnerable range: any version before 2.20.0 is affected. For example, versions like 2.19.x, 2.18.x, 2.17.x and earlier are within the vulnerable range.
    Affected if If the installed version is less than 2.20.0 (for example, 2.19.1, 2.18.0, etc.), the device is running a vulnerable version.
  4. Check device security posture
    Verify if the device has screen lock enabled (Settings > Security > Screen lock) and if full disk encryption is active. These are relevant because the vulnerability allows physical access bypass.
    Affected if If the device lacks screen lock or encryption, the physical access attack vector is more feasible, though the app version vulnerability exists regardless.

The environment is affected if the installed ownCloud Android client version is below 2.20.0, regardless of device security settings, as the version itself contains the access control flaw.

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 2.20.0 or later
Fixed in 2.20.0
Interim mitigation

Update the ownCloud Android application to version 2.20 or later. Additionally, enforce strong device-level security measures including screen locks, encryption, and remote wipe capabilities to mitigate physical access attacks.

Recommended fix Moderate confidence

ownCloud Android app version 2.20.0 or later

  1. 1. Open the Google Play Store on the Android device
  2. 2. Search for "ownCloud" or open the existing ownCloud app
  3. 3. If an update is available, tap "Update" to install version 2.20.0 or later
  4. 4. Alternatively, download the latest ownCloud Android app from the Google Play Store to ensure version 2.20.0 or newer is installed
  5. 5. Verify the installed version in the app settings is 2.20.0 or higher

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

Fix this in Owncloud Client Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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