CVE-2015-9045
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 all Qualcomm products with Android releases from CAF using the Linux kernel, a vulnerability exists in GERAN where a buffer can be overflown while taking power measurements.
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 · low confidenceA buffer overflow vulnerability exists in the GERAN (GSM/EDGE Radio Access Network) component of Qualcomm baseband firmware. The overflow occurs specifically during power measurement operations, potentially allowing remote code execution or denial of service via malicious network signaling.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the baseband chipsetCheck if the device uses a Qualcomm baseband chipset. On Android, go to Settings > About Phone > Baseband version, or use terminal commands like 'getprop gsm.version.baseband' or 'cat /proc/cpuinfo' to look for Qualcomm components.Affected if The device does not have a Qualcomm baseband (the vulnerability is in Qualcomm firmware only)
-
Check the baseband firmware versionRetrieve the baseband version string from the device. On Android, use 'getprop gsm.version.baseband' or check Settings > About Phone > Baseband. Compare this version against any publicly released Qualcomm baseband patch versions for CVE-2015-9045 from Qualcomm's security advisories.Affected if The baseband version is older than the patched version released by Qualcomm for this CVE
-
Verify GERAN/GSM/EDGE capabilityConfirm the device supports GSM, EDGE, or GERAN network modes. Check network settings or use 'getprop gsm.network.type' to see supported radio technologies.Affected if The device supports GSM/EDGE networks (this is the attack surface for exploitation)
-
Confirm power measurement feature is activeThe vulnerability occurs during power measurement operations in the GERAN component. This is an internal baseband function triggered during network cell measurements. No direct user config exists; it is inherent to GSM/EDGE radio operation.Affected if The device uses GSM/EDGE connections, which triggers the vulnerable power measurement code path
A device is affected if it has a Qualcomm baseband chipset operating in GSM/EDGE network mode with a baseband version predating the CVE-2015-9045 patch.
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 dataApply vendor-supplied firmware updates from Qualcomm and device manufacturers. Prioritize patching on devices operating in GSM/EDGE network environments given the attack surface.
- Consultation8.0 h
- Implementation2.0 h
- Testing16.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,704.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9045 — 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-2015-9045 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