dbcve.org
AndroidOperating system · Google

CVE-2023-21062

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 DoSetTempEcc of imsservice.cpp, there is a possible out of bounds read 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-243376770References: 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 · high confidence

A bounds check error in the DoSetTempEcc function within imsservice.cpp causes an out-of-bounds read vulnerability. The incorrect bounds check allows a local attacker to read memory beyond allocated buffers, potentially enabling privilege escalation from the application's privileges to System level on Android devices.

MitigationApply the Android security patch for the relevant monthly bulletin (this vulnerability was addressed in Android's security updates). Keep the Android device or system updated to receive vendor-supplied patches.

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. Check Android security patch level
    Go to Settings > About Phone > Security Patch Level, or run 'adb shell getprop ro.build.version.security_patch'
    Affected if The security patch level is earlier than the month this CVE was fixed (refer to Android Security Bulletin)
  2. Verify imsservice is present
    Run 'adb shell pm list packages | grep ims' or check for imsservice process with 'adb shell ps -A | grep ims'
    Affected if The IMS service package or process is found on the device (vulnerable component is present)
  3. Check Android OS version
    Run 'adb shell getprop ro.build.version.release' or check in Settings > About Phone > Android version
    Affected if The Android version does not have the corresponding security update applied (patch level below the fix date)
  4. Identify if IMS (IP Multimedia Subsystem) is enabled
    Check Settings > Network & Internet > Mobile Network > Advanced > IMS status, or inspect 'adb shell settings get global voLTE_implemented'
    Affected if IMS/VoLTE is enabled and the device is not fully patched

A device is affected if it runs an Android version without the corresponding security patch that addresses this vulnerability in the imsservice DoSetTempEcc function, particularly when IMS is enabled.

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 Android security patch for the relevant monthly bulletin (this vulnerability was addressed in Android's security updates). Keep the Android device or system updated to receive vendor-supplied patches.

Recommended fix Moderate confidence

Android Security Patch Level that includes the fix for A-243376770 (contact device vendor for specific build/level)

  1. Contact your Android device manufacturer or carrier for the specific security patch containing the fix for Android ID A-243376770
  2. Apply the latest Android security update available for your device
  3. For enterprise deployments, verify the security patch level through device management policies
  4. The vulnerability is in the IMS service (imsservice.cpp); ensure your Android version includes the fix for this specific issue
  5. If your device is no longer receiving security updates, consider migrating to a supported device
Caveat Devices at end-of-life may not receive patches; ensure backup/recovery plans are in place before updating

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 / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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