AndroidOperating system · Google

CVE-2015-8546

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
An issue was discovered on Samsung mobile devices with software through 2015-11-12, affecting the Galaxy S6/S6 Edge, Galaxy S6 Edge+, and Galaxy Note5 with the Shannon333 chipset. There is a stack-based buffer overflow in the baseband process that is exploitable for remote code execution via a fake base station. The Samsung ID is SVE-2015-5123 (December 2015).

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 confidence

A stack-based buffer overflow vulnerability in the baseband processor of Samsung Galaxy S6/S6 Edge/S6 Edge+ and Note5 devices with Shannon333 chipset allows remote code execution via a malicious fake base station. The attacker exploits the baseband process by sending specially crafted messages from a rogue cell tower.

MitigationApply Samsung firmware update SVE-2015-5123 (December 2015 patch bundle). Users should ensure their devices receive the latest carrier/Samsung baseband firmware updates. Consider retiring or isolating affected devices that can no longer receive security updates.

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 data
AndroidOperating system
Affected:all versions

CVSS 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.1/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Check if the device is a Samsung Galaxy S6, S6 Edge, S6 Edge+, or Note5 by going to Settings > About Phone > Model Number
    Affected if Device model is NOT one of Galaxy S6, S6 Edge, S6 Edge+, or Note5 - the vulnerability does not apply
  2. Verify chipset type
    Check the baseband/processor chipset information via Settings > About Phone > Hardware or use a system info app to confirm if the device uses the Shannon333 chipset
    Affected if Chipset is NOT Shannon333 - this specific vulnerability only affects devices with Shannon333 baseband processor
  3. Check baseband firmware version
    View baseband version in Settings > About Phone > Baseband version or via *#0011# in phone dialer. Compare this version against the December 2015 patch bundle (SVE-2015-5123)
    Affected if Baseband firmware version is older than the December 2015 update and has not received the SVE-2015-5123 patch bundle - the buffer overflow vulnerability is present
  4. Confirm network exposure
    The vulnerability is exploitable when the device connects to a malicious fake base station (rogue cell tower). Check if the device has mobile network connectivity in areas with unknown or suspicious cell towers
    Affected if Device has mobile data/cellular connectivity and connects to cell towers - the attack vector requires the baseband processor to receive specially crafted messages from a rogue base station

User is affected if the device is a Samsung Galaxy S6/S6 Edge/S6 Edge+/Note5 with Shannon333 chipset AND the baseband firmware has not been updated to include the December 2015 security patch SVE-2015-5123.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Samsung firmware update SVE-2015-5123 (December 2015 patch bundle). Users should ensure their devices receive the latest carrier/Samsung baseband firmware updates. Consider retiring or isolating affected devices that can no longer receive security updates.

Fix this in Android Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,608.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-8546 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-8546 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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