LiveActive security incident?Get immediate response
CVE Record

CVE-2023-20942: In openMmapStream of AudioFlinger.cpp, there is a possible way to record audio without displaying the micro...

In openMmapStream of AudioFlinger.cpp, there is a possible way to record audio without displaying the microphone privacy indicator due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Android flaw could let a local app record audio without showing the microphone privacy indicator. The main business concern is covert audio collection on affected Android 12, 12L, and 13 devices. The source bundle does not show active exploitation or a CVSS score.

Executive priority

Treat this as a privacy-impacting mobile patching issue. It does not justify emergency response from the supplied evidence, but affected Android fleets should be brought to the July 2023 patch level or later during normal high-priority mobile maintenance.

Technical view

CVE-2023-20942 is a logic error in AudioFlinger.cpp openMmapStream affecting Android 12, 12L, and 13. Google describes local escalation of privilege with no extra execution privileges and no user interaction. References include Android frameworks/av commits and the July 2023 Android Security Bulletin.

Likely exposure

Exposure is most relevant to fleets running Android 12, 12L, or 13 without the July 2023 Android security update or equivalent OEM backport. Devices on other versions are listed as unaffected in the supplied affected data.

Exploitation context

The source bundle says exploitation needs local access but no user interaction or additional execution privileges. It does not cite public exploitation, weaponized proof of concept, or CISA KEV listing, so active exploitation should not be claimed.

Researcher notes

The bundle lists CWE-326, but the description points to a logic error in AudioFlinger privacy-indicator handling. No CVSS vector is supplied. Research should focus on patch presence, Android branch coverage, and whether OEM builds incorporated the linked frameworks/av commits.

Mitigation direction

  • Apply the July 2023 Android Security Bulletin update or later OEM security update.
  • Confirm OEM firmware includes the referenced Android frameworks/av fixes.
  • Prioritize managed devices with microphone access granted to untrusted apps.
  • Review vendor guidance if devices cannot receive current Android security patches.

Validation and detection

  • Inventory Android devices running versions 12, 12L, and 13.
  • Check each device security patch level for July 2023 or later.
  • Verify OEM release notes reference CVE-2023-20942 or July 2023 Android fixes.
  • Review app microphone permissions on affected managed devices.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-326: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-20942 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroid13, 12L, 12unaffected
Weakness

CWE details

CWE-326

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-326 · source CWE mapping

Inadequate Encryption Strength

Inadequate Encryption Strength represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs