CVE-2015-9065
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 UE can respond to a UEInformationRequest before Access Stratum security is established.
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 confidenceA Qualcomm baseband vulnerability in Android devices allows a User Equipment (UE) to respond to UEInformationRequest messages before Access Stratum (AS) security is established, enabling potential information disclosure or manipulation of cellular protocol communications before cryptographic protections are in place.
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 processor typeCheck the device's baseband or modem processor. On Android, go to Settings > About Phone > Baseband version or use terminal command 'getprop gsm.version.baseband'. Look for 'Qualcomm' in the output.Affected if The device does not use a Qualcomm baseband processor - this CVE specifically affects Qualcomm basebands
-
Confirm baseband firmware versionRecord the full baseband version string shown (e.g., from Settings > About Phone > Baseband version). Note the complete version number including any build numbers or letter suffixes.Affected if Unable to retrieve a baseband version or the version shows as unknown/unavailable
-
Compare against patched firmware versionsResearch the specific patched baseband firmware version for your device model and carrier. Check your device OEM's security advisory or release notes for CVE-2015-9065. Compare your installed baseband version to the fixed version for your exact device model.Affected if The installed baseband version predates the OEM-provided patch for this vulnerability and no subsequent security update has been applied
-
Verify Android security patch levelCheck the Android security patch level: Settings > About Phone > Android version or run 'getprop ro.build.version.security_patch'. This indicates whether OEM security updates addressing the baseband flaw have been installed.Affected if The security patch level is earlier than the date when your OEM released the fix for CVE-2015-9065, or shows as unknown/not set
The device is affected if it uses a Qualcomm baseband processor and either the baseband firmware predates the OEM patch for this vulnerability or the Android security patch level is below the date when the fix was released.
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 Qualcomm firmware updates and subsequent Android security patches from device OEMs; enterprise environments should ensure mobile device management policies enforce timely patch deployment.
- Consultation8.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,672.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9065 — 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-9065 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