dbcve.org
AndroidOperating system · Google

CVE-2022-42500

MEDIUM · 6.7 CVSS v3.1 Published 2023-03-24
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 OEM_OnRequest of sced.cpp, there is a possible shell command execution due to improper input validation. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-239701389References: N/A

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

This is a local privilege escalation vulnerability in the Android kernel's sced.cpp file, specifically in the OEM_OnRequest function. The vulnerability stems from improper input validation that could allow shell command execution. Exploitation requires System-level privileges on the device, but no user interaction is needed.

MitigationApply the latest Android security patches from your device OEM, as this kernel-level vulnerability requires source code fixes to the input validation in OEM_OnRequest. For developers with access to the affected code, implement strict input validation and sanitization before any shell command execution.

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:all versions

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. Confirm Android version and security patch level
    Go to Settings > About Phone > Android version and Build number to note the current Android version and security patch date
    Affected if The device is running any Android version without the specific kernel patch for CVE-2022-42500 - which affects all versions per the advisory
  2. Identify if the sced daemon or OEM service exists
    Check for the presence of the sced (Secure Channel Execution Daemon) or OEM-related services by examining /system/bin or /vendor/bin directories: 'ls -la /system/bin/sce* /vendor/bin/sce* 2>/dev/null' or 'ps -A | grep -i sce'
    Affected if The sced daemon or OEM service is present and running, as this contains the vulnerable OEM_OnRequest function in sced.cpp
  3. Verify if OEM_OnRequest function is exposed
    Examine the system's SELinux policy or service definitions for any OEM-related IPC channels: 'getprop | grep -i oem' and check for vendor-specific services in /vendor or /system that expose OEM functionality
    Affected if The device exposes OEM request handling functionality through the vulnerable OEM_OnRequest code path
  4. Check for system-level access
    Determine if your application or process has system-level (system_server) or root privileges: 'id' command shows UID/GID, and 'whoami' confirms the current context
    Affected if The attacker already has system-level privileges, which is the prerequisite for exploiting this vulnerability to escalate to root
  5. Review kernel or vendor binary for the vulnerable code pattern
    If you have root access, examine the sced binary or shared libraries in /vendor/lib or /system/lib for the OEM_OnRequest function signature using strings or objdump: 'strings /vendor/bin/sced 2>/dev/null | grep -i OnRequest' or reverse engineer the binary
    Affected if The binary contains the OEM_OnRequest function without proper input validation checks on the command execution path

A device is affected if it runs any Android version, has the sced/OEM service exposing the vulnerable OEM_OnRequest function, and the attacker already possesses system-level privileges on that device.

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 the latest Android security patches from your device OEM, as this kernel-level vulnerability requires source code fixes to the input validation in OEM_OnRequest. For developers with access to the affected code, implement strict input validation and sanitization before any shell command execution.

Recommended fix Moderate confidence

Android security patch level November 2022 or later (2022-11-01 or higher)

  1. Apply the Android security patch level that includes the fix for Android ID A-239701389
  2. Verify the device has received the security update containing the fix for this vulnerability
  3. On the affected Android device, go to Settings > Security > Security update to confirm the patch level

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

Fix this in Android 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-2022-42500 — 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-42500 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