dbcve.org
AndroidOperating system · Google

CVE-2022-42523

MEDIUM · 6.7 CVSS v3.1 Published 2022-12-16
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 fillSetupDataCallInfo_V1_6 of ril_service_1_6.cpp, there is a possible out of bounds write due to an incorrect bounds check. 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-243376893References: 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 buffer overflow vulnerability in Android's Radio Interface Layer (RIL) where the function fillSetupDataCallInfo_V1_6 in ril_service_1_6.cpp performs an incorrect bounds check, leading to an out-of-bounds write. Since the RIL runs with System-level privileges, this allows a local attacker to escalate privileges. No user interaction is required.

MitigationApply the correct bounds check fix in the fillSetupDataCallInfo_V1_6 function in ril_service_1_6.cpp to prevent the out-of-bounds write. Rebuild and deploy the updated RIL/system component as part of an Android security patch.

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. Identify Android version
    Go to Settings > About Phone > Android version or run 'getprop ro.build.version.release' via ADB
    Affected if The device runs any version of Android and has not applied the November 2022 security patch or later
  2. Check security patch level
    Go to Settings > About Phone > Security patch level or run 'getprop ro.build.version.security_patch' via ADB
    Affected if The security patch level is earlier than November 2022, indicating the fix is not applied
  3. Verify RIL component presence
    Check for the existence of the RIL library. On most devices it is located at /vendor/lib64/librilutil.so or /system/lib64/librilutils.so. Run 'find / -name "*ril*" -type f 2>/dev/null | head -20' via ADB shell
    Affected if The device has a RIL library present, which is required for the vulnerability to be exploitable
  4. Confirm vulnerable function exists
    Check the RIL library for the fillSetupDataCallInfo_V1_6 function. Use 'strings <ril_library_path> | grep fillSetupDataCallInfo_V1_6' or disassemble the library
    Affected if The function fillSetupDataCallInfo_V1_6 exists in the RIL library, indicating the vulnerable code path is present

A device is affected if it runs any Android version without the November 2022 security patch and contains the vulnerable fillSetupDataCallInfo_V1_6 function in its RIL component.

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 correct bounds check fix in the fillSetupDataCallInfo_V1_6 function in ril_service_1_6.cpp to prevent the out-of-bounds write. Rebuild and deploy the updated RIL/system component as part of an Android security patch.

Recommended fix Moderate confidence

Apply Android Security Patch Level November 2022 or later (specific to your device model)

  1. Check your Android device's current security patch level in Settings > About Phone > Security Patch Level
  2. Ensure your device has received the November 2022 Android Security Update or later which contains the fix for CVE-2022-42523
  3. If your device manufacturer has not released this update, contact your device vendor or carrier for patch availability
  4. Consider upgrading to a newer Android version if your device is no longer supported with security updates
Caveat Some older devices may no longer receive security updates from manufacturers; in such cases, consider replacing with a currently supported device

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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