dbcve.org
AndroidOperating system · Google

CVE-2022-20068

MEDIUM · 6.7 CVSS v3.1 Published 2022-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
In mobile_log_d, there is a possible symbolic link following due to an improper link resolution. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06308907; Issue ID: ALPS06308907.

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

In mobile_log_d, there is a symbolic link following vulnerability due to improper link resolution. The logging daemon does not properly validate file paths before accessing them, allowing an attacker to manipulate file access through symbolic links. This enables local privilege escalation from System execution privileges. No user interaction is required.

MitigationApply vendor patch ALPS06308907 which adds proper symbolic link resolution checks. Consider implementing O_NOFOLLOW flags or file type validation for file operations in mobile_log_d.

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
AndroidOperating system
Affected:= 10.0= 11.0= 12.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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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 Android version
    Check the device or system settings for the Android OS version. On most Android devices, this is found under Settings > About Phone > Android version.
    Affected if The installed Android version is 10.0, 11.0, or 12.0 (exact matches)
  2. Locate mobile_log_d service
    Search for the mobile_log_d binary or service on the device. This is typically found in system partitions or /vendor/bin/ directories. Use 'find / -name mobile_log_d 2>/dev/null' or check process list with 'ps -A | grep mobile_log_d'.
    Affected if The mobile_log_d service or binary is present and running on the device
  3. Verify service privileges
    Check the privileges of the mobile_log_d process. Use 'ps -A | grep mobile_log_d' to find the process, then examine its user/group context. The vulnerability requires the service to run with System-level privileges.
    Affected if mobile_log_d runs with System user privileges (uid 1000) or elevated system permissions
  4. Check for accessible file operations
    Examine the mobile_log_d configuration or log directories it accesses. Look for world-writable log directories or configuration paths that could be manipulated via symbolic links.
    Affected if mobile_log_d accesses log files or configuration paths in directories with broad write permissions

A device is affected if it runs Android 10.0, 11.0, or 12.0 and has the mobile_log_d service running with System-level privileges in an accessible configuration.

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

Apply vendor patch ALPS06308907 which adds proper symbolic link resolution checks. Consider implementing O_NOFOLLOW flags or file type validation for file operations in mobile_log_d.

Recommended fix Moderate confidence

Android Security Patch Level June 2022 or later (contact OEM for specific firmware version)

  1. 1. Check the current Android Security Patch Level on the device via Settings > About Phone > Build Number or Settings > Security > Security Patch Level
  2. 2. Apply the latest Android system updates from the device manufacturer (OEM)
  3. 3. Verify the device has the June 2022 Android Security Bulletin or later patches applied
  4. 4. For enterprise/managed devices, ensure Mobile Device Management (MDM) policies enforce system updates
  5. 5. If the OEM has not released a patch, contact the device manufacturer for patch ALPS06308907
Caveat Some OEMs may stop providing updates for older devices; verify device is still within support window

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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