dbcve.org
AndroidOperating system · Google

CVE-2023-32847

HIGH · 7.8 CVSS v3.1 Published 2023-12-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 audio, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation. Patch ID: ALPS08241940; Issue ID: ALPS08241940.

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 in the audio subsystem due to a missing bounds check. The issue allows local privilege escalation but requires user interaction to trigger, indicating the attack likely involves processing malicious audio data through the affected component.

MitigationApply the vendor patch ALPS08241940 which adds proper bounds checking to prevent the out-of-bounds write condition in the audio component.

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 version
    Go to Settings > About Phone > Android version or run 'getprop ro.build.version.release' via ADB
    Affected if The version listed is exactly 12.0 or 13.0
  2. Verify audio service is active
    Run 'dumpsys audio' via ADB shell to confirm the audio service is running and accessible
    Affected if The audio service responds and shows active audio configurations or streams
  3. Check audio HAL implementation
    Run 'getprop audio.hal.version' or check '/vendor/etc/audio_policy_configuration.xml' via ADB to identify the audio HAL in use
    Affected if A custom or third-party audio HAL is loaded without the vendor patch ALPS08241940 applied

You are affected if your device runs Android 12.0 or 13.0 and uses the audio subsystem without the ALPS08241940 patch applied.

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 vendor patch ALPS08241940 which adds proper bounds checking to prevent the out-of-bounds write condition in the audio component.

Recommended fix Moderate confidence

Latest available Android security patch level (July 2023 or later security update for Android 12.0/13.0 devices with MediaTek chipsets)

  1. Check your Android device for the latest system updates by going to Settings > System > Software Update
  2. Contact your device manufacturer (OEM) to confirm they have incorporated the MediaTek security patch ALPS08241940
  3. Apply the latest Android security patch level available for your device (typically the July 2023 or later security bulletin for Android 12.0 and 13.0)
  4. If your OEM has not released an update containing this patch, consider applying any available vendor firmware updates that include MediaTek audio fixes
Caveat OEMs control deployment timing; some older devices may not receive patches; check with your device vendor for specific update availability

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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