CVE-2015-3843
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 · uneditedThe SIM Toolkit (STK) framework in Android before 5.1.1 LMY48I allows attackers to (1) intercept or (2) emulate unspecified Telephony STK SIM commands via an application that sends a crafted Intent, related to com/android/internal/telephony/cat/AppInterface.java, aka internal bug 21697171.
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 vulnerability in Android's SIM Toolkit (STK) framework before version 5.1.1 allows malicious applications to intercept or emulate Telephony STK SIM commands by sending crafted Intents. The flaw exists in the Intent handling within com/android/internal/telephony/cat/AppInterface.java, enabling unauthorized access to sensitive SIM card interactions.
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<= 5.1CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
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.
-
Check Android OS versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if Version is 5.1 or lower (5.1.0, 5.0.x, 4.x, etc.)
-
Confirm STK capability existsCheck if the device has SIM Toolkit functionality - look for a STK or SIM Toolkit app in the app drawer, or check for 'com.android.stk' package via 'pm list packages' in ADBAffected if STK application or package is present on the device
-
Verify build is not the patched releaseCheck Settings > About Phone > Build number, or run 'getprop ro.build.display.id' via ADB - look specifically for builds that are NOT 'LMY48I' or laterAffected if Build number is below LMY48I (e.g., LMY47V, LMY47D, or any earlier 5.1 build)
A device is affected if it runs Android 5.1 or earlier with an active STK component present, and its build is not LMY48I or later.
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.
dbcve · scopedUpdate affected devices to Android 5.1.1 LMY48I or later, which contains the patch for this STK framework vulnerability. No configuration-based workarounds exist as this is a platform-level code flaw.
Android 5.1.1 LMY48I or later
- Check current Android version in Settings > About Phone > Android version
- Ensure the device is running Android 5.1.1 LMY48I or later to have the fix applied
- Check for system updates: Settings > About Phone > Check for updates
- If an OTA update is available, download and install it
- If no OTA update is available from the carrier/OEM, contact the device manufacturer or wireless carrier for the update
- After updating, verify the Android version is 5.1.1 LMY48I or higher in Settings > About Phone
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3843 — 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-3843 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