dbcve.org
AndroidOperating system · Google

CVE-2022-42513

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 ProtocolEmbmsBuilder::BuildSetSession of protocolembmsbuilder.cpp, 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.Product: AndroidVersions: Android kernelAndroid ID: A-241763204References: 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

This is a kernel-level vulnerability in Android's eMBMS (Enhanced Multimedia Broadcast Multicast Service) protocol builder. The BuildSetSession function in protocolembmsbuilder.cpp lacks proper bounds checking, allowing an out-of-bounds write that can be exploited for local privilege escalation from System privileges. No user interaction is required for exploitation.

MitigationApply the latest Android security patch level containing the fix for A-241763204; this is a kernel-level fix requiring a system OTA update rather than application-level remediation.

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. Verify eMBMS feature status
    Check if eMBMS (Enhanced Multimedia Broadcast Multicast Service) is enabled on the Android device. This can be done via: 1) Settings > Network & Internet > Mobile Network > Enhanced Messaging (or similar path depending on Android version), 2) Using 'settings get global embms_enable' via ADB shell, or 3) Checking /system/etc/permissions/android.hardware.telephony.embms.xml or vendor-specific embms configuration files
    Affected if eMBMS is enabled on the device, as this is the attack surface for the vulnerable BuildSetSession function in protocolembmsbuilder.cpp
  2. Check Android Security Patch Level
    Run 'getprop ro.build.version.security_patch' via ADB shell to retrieve the installed security patch level. Alternatively, check Settings > About Phone > Android version > Security patch level
    Affected if The security patch level is earlier than the one containing the fix for A-241763204 (the vulnerability was patched in post-December 2022 Android security updates)
  3. Verify kernel version and build
    Run 'uname -a' and 'getprop ro.build.fingerprint' via ADB shell to identify the exact Android build. Cross-reference the build fingerprint with Google's monthly Android securitybulletin to determine if the A-241763204 fix is included
    Affected if The kernel/build does not include the December 2022 or later security update that addresses the out-of-bounds write in BuildSetSession

The environment is affected if eMBMS is enabled AND the device is running an Android security patch level prior to the fix for A-241763204 (December 2022 or later patches).

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 latest Android security patch level containing the fix for A-241763204; this is a kernel-level fix requiring a system OTA update rather than application-level remediation.

Recommended fix Moderate confidence

Apply the latest Android security update (monthly security patch level that includes CVE-2022-42513 fix)

  1. 1. Check your Android device's current security patch level by going to Settings > About Phone > Security Patch Level
  2. 2. Identify the Android Security Bulletin month that addressed CVE-2022-42513 (Android ID: A-241763204) - this vulnerability was addressed in a monthly Android security update
  3. 3. Apply the latest Android security update for your device to obtain the fix
  4. 4. If your device manufacturer has stopped providing updates, consider upgrading to a device that receives regular security patches
  5. 5. Verify the security patch level has been updated after applying the update
Caveat Some older devices may no longer receive monthly security updates from manufacturers; consider device upgrade if update is unavailable

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

Fix this in Android Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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