CVE-2023-48415
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 · uneditedIn Init of protocolembmsadapter.cpp, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
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 confidenceIn the Init function of protocolembmsadapter.cpp, an out of bounds read vulnerability exists due to a missing bounds check during buffer handling. This allows a local attacker to read memory beyond allocated buffers, potentially exposing sensitive information without requiring any special privileges or user interaction.
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 dataall versionsCVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if the device runs AndroidCheck the system property 'ro.build.version.sdk' or inspect /system/build.prop for 'ro.build.version.release'Affected if The device is running Google Android OS
-
Check for presence of the protocolembmsadapter componentLook for the file protocolembmsadapter.cpp or the compiled binary/library containing this module in the Android system partition (typically under /system/lib/ or /vendor/lib/)Affected if The protocolembmsadapter component exists on the device
-
Determine if eMBMS feature is enabledCheck Android system properties using 'getprop' command for eMBMS-related properties (such as 'ro.telephony.emmcservice' or similar carrier-specific properties), or inspect /system/etc/emmcservice_config.xml if presentAffected if eMBMS (Multimedia Broadcast Multicast Service) is enabled or provisioned on the device
-
Verify the vulnerable code path can be triggeredReview telphony logs (logcat -b radio) for eMBMS initialization messages that exercise the Init function in protocolembmsadapter during device boot or radio service startupAffected if The eMBMS protocol adapter initialization runs and processes buffer data without proper bounds validation
A user is affected if the device runs Android and has the protocolembmsadapter component with eMBMS feature enabled, allowing the vulnerable Init function to execute and perform out-of-bounds reads on buffer data.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataAdd proper bounds validation checks before buffer access operations in the Init function. Ensure all array/buffer indices and sizes are validated against actual buffer dimensions before read operations.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-48415 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-48415 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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