dbcve.org
AndroidOperating system · Google

CVE-2023-20658

MEDIUM · 6.7 CVSS v3.1 Published 2023-04-06
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 isp, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07537393; Issue ID: ALPS07180396.

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

An out-of-bounds write vulnerability exists in the ISP (Image Signal Processor) component due to a missing bounds check. An attacker with system-level privileges could exploit this memory corruption issue to escalate privileges to root.

MitigationApply vendor patch ALPS07537393 which adds the missing bounds check in the ISP component. This is a targeted patch that should be tested thoroughly on the specific device model.

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:= 12.0= 13.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. Verify Android version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if Version is 12.0 or 13.0 exactly (not a later security patch update)
  2. Confirm ISP hardware presence
    Check device specifications for ISP (Image Signal Processor) in the SoC, or inspect kernel modules for isp-related drivers via 'ls /vendor/lib/modules/' or check /proc/device-tree/ for ISP nodes
    Affected if Device has an ISP component (present in most Android smartphones with cameras)
  3. 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 the date when ALPS07537393 was released (patch not yet applied)
  4. Verify vendor-specific ISP patch status
    Consult device manufacturer documentation or security bulletin for patch ALPS07537393 status, or check vendor-specific build properties via 'getprop' | grep -i isp
    Affected if Vendor patch ALPS07537393 has not been applied to the ISP component

Device is affected if running Android 12.0 or 13.0 and the ISP component has not received vendor patch ALPS07537393 (check via security patch level or vendor documentation).

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 ALPS07537393 which adds the missing bounds check in the ISP component. This is a targeted patch that should be tested thoroughly on the specific device model.

Recommended fix Moderate confidence

Android 12.0/13.0 with the security patch level containing ALPS07537393 (typically included in Android Security Bulletins from early 2023)

  1. 1. Check the Android Security Bulletin for the month the patch ALPS07537393 was released (refer to source: corp.mediatek.com)
  2. 2. Apply the corresponding Android system security update that includes the MediaTek ISP fix
  3. 3. Verify the device has the latest security patch level installed via Settings > About Phone > Security Patch Level
  4. 4. If the device manufacturer has released a specific firmware update incorporating MediaTek patch ALPS07537393, apply that update
Caveat Security updates are low-risk; ensure backup of data before applying major system updates

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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