CVE-2024-47015
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 ProtocolMiscHwConfigChangeAdapter::GetData() of protocolmiscadapter.cpp, there is a possible out-of-bounds read due to a missing bounds check. This could lead to local information disclosure with baseband firmware compromise required. 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 · moderate confidenceAn out-of-bounds read vulnerability exists in ProtocolMiscHwConfigChangeAdapter::GetData() in protocolmiscadapter.cpp due to a missing bounds check. This allows local information disclosure but requires prior compromise of the baseband firmware. The vulnerability does not require user interaction to exploit.
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 the baseband modem componentCheck your device's baseband/modem firmware version and model through Android settings (Settings > About Phone > SIM Status or via 'getprop' command for vendor-specific baseband info)Affected if The device uses a baseband processor where ProtocolMiscHwConfigChangeAdapter::GetData() in protocolmiscadapter.cpp handles hardware configuration data
-
Verify baseband firmware integrityCheck if your device supports and has secure boot enabled for the baseband subsystem, or inspect any available firmware integrity verification logsAffected if Baseband firmware has been compromised prior to this vulnerability being triggered, which is a prerequisite for exploitation
-
Inspect the protocolmiscadapter componentIf you have access to baseband firmware binaries, search for the ProtocolMiscHwConfigChangeAdapter::GetData function and examine memory access patterns in the protocolmiscadapter.cpp compiled binaryAffected if The GetData() function lacks proper bounds checking when accessing memory buffers, allowing out-of-bounds read access
-
Check for information disclosure indicatorsMonitor baseband-related logs or memory dumps for unexpected data exposure in the hardware configuration change adapter data pathAffected if The device exhibits out-of-bounds read behavior leading to local information disclosure from memory
The device is affected if it runs Google Android with a baseband modem where the ProtocolMiscHwConfigChangeAdapter::GetData() function is present and the baseband firmware has been compromised, since this vulnerability requires prior baseband firmware compromise as an exploitation prerequisite.
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 dataImplement proper bounds checking in the GetData() function before accessing memory buffers. Since baseband firmware compromise is required as a prerequisite, ensure firmware integrity verification and secure boot mechanisms are in place to prevent the initial compromise.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47015 — 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-2024-47015 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