CVE-2015-9034
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 string can fail to be null-terminated in SIP leading to a buffer overflow.
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 confidenceA buffer overflow vulnerability exists in the SIP (Session Initiation Protocol) implementation within Qualcomm Android releases using the Linux kernel. The issue stems from a string failing to be properly null-terminated, allowing an attacker to potentially overwrite adjacent memory and achieve remote code execution. This kernel-level flaw affects all Qualcomm devices using CAF Android releases.
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.
-
Confirm Qualcomm chipset presenceCheck if the device uses a Qualcomm Snapdragon chipset by reviewing /proc/cpuinfo or system information settings. Look for 'Qualcomm' or 'Snapdragon' in the hardware identifier.Affected if The device does not use a Qualcomm chipset - the vulnerability is specific to Qualcomm CAF Android releases.
-
Verify SIP application usageCheck if any SIP-based applications or services are installed and active on the device. Review running processes for SIP-related daemons or examine installed applications for VoIP/SIP clients.Affected if No SIP applications are installed or used - the exploitation requires SIP traffic to be processed by the vulnerable kernel component.
-
Check kernel version against fixed patch levelRun 'uname -r' or examine /proc/version to obtain the kernel version. Compare against the Android security patch level in system settings under 'About Phone' > 'Android version' or 'Security patch level'.Affected if The kernel version predates the vendor patch or the security patch level is earlier than February 2016 - the vulnerability exists in unpatched kernels.
-
Inspect SIP kernel module loadingCheck if the SIP kernel module (often related to net/sip or protocol handlers) is loaded by examining 'lsmod' output and /proc/modules for sip-related modules.Affected if A SIP-related kernel module is loaded and the kernel version is unpatched, the vulnerability is active in memory.
A user is affected if they use a Qualcomm-based Android device with an unpatched kernel that processes SIP traffic through the vulnerable code path.
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 the vendor-supplied patch from Qualcomm/Google via system update. Until the patch is deployed, consider network-level filtering of SIP traffic to reduce exposure, though this is only a temporary measure.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9034 — 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-9034 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