dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2024-50657

MEDIUM · 6.8 CVSS v3.1 Published 2024-11-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
An issue in Owncloud android apk v.4.3.1 allows a physically proximate attacker to escalate privileges via the PassCodeViewModel class, specifically in the checkPassCodeIsValid method

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 app v4.3.1 contains a vulnerability in the PassCodeViewModel class, specifically in the checkPassCodeIsValid method. A physically proximate attacker with temporary device access can exploit this flaw to bypass or manipulate passcode validation, achieving unauthorized privilege escalation.

MitigationApply vendor patch when available; ensure devices are physically secured, encrypted, and use secure boot mechanisms to limit physical attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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. Identify ownCloud Android app installation
    Check device for installed ownCloud Android app via Settings > Apps > ownCloud (or equivalent package manager: adb shell pm list packages | grep owncloud)
    Affected if ownCloud Android app is not installed on the device
  2. Determine installed app version
    Access app info screen (Settings > Apps > ownCloud > App info) or use adb shell dumpsys package com.owncloud.android to read versionName from the package metadata
    Affected if Installed version matches or is prior to v4.3.1 (the vulnerable version)
  3. Verify passcode protection is enabled
    Open ownCloud Android app > Settings > Security > Passcode (or similar) - check if a passcode is set and enforced for app access
    Affected if Passcode protection feature is enabled and configured in the app
  4. Assess physical access exposure
    Evaluate whether the device could be accessed temporarily by unauthorized physical proximity (left unattended, shared device, stolen briefly)
    Affected if Device can be accessed physically by threat actors (even briefly)

User is affected if ownCloud Android app v4.3.1 or earlier is installed with passcode protection enabled and the device has any risk of temporary physical access by unauthorized parties.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch when available; ensure devices are physically secured, encrypted, and use secure boot mechanisms to limit physical attack surface.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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