CVE-2015-2002
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 ESRI ArcGis Runtime SDK before 10.2.6-2 for Android might allow attackers to execute arbitrary code by leveraging a finalize method in a Serializable class that improperly passes an attacker-controlled pointer to a native function.
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 confidenceThe ESRI ArcGIS Runtime SDK for Android before version 10.2.6-2 contains a critical deserialization vulnerability where a finalize() method in a Serializable class improperly passes an attacker-controlled pointer to a native function, allowing arbitrary code execution.
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< 10.2.6-2CVSS 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 ArcGIS Runtime SDK dependencyExamine build configuration files (build.gradle, pom.xml, or libs/ directory) for Esri ArcGIS Runtime SDK for Android libraries. Search for files containing 'arcgis', 'runtime', or 'esri' in dependencies.Affected if The SDK is present in the project dependencies
-
Determine installed SDK versionLocate the specific version number in the dependency declaration (e.g., compile 'com.esri.arcgis.android:arcgis-android:10.2.5') or the corresponding JAR/aar library file name.Affected if A version number is found that is less than 10.2.6-2
-
Verify vulnerability applicabilityConfirm the application deserializes data from external or untrusted sources into ArcGIS objects. Check code for ObjectInputStream usage with ArcGIS Serializable classes, or network/data import features.Affected if The application deserializes potentially attacker-controlled data into ArcGIS Runtime objects
If your project uses ESRI ArcGIS Runtime SDK for Android version 10.2.6-2 or earlier and deserializes untrusted data, your environment is affected by this vulnerability.
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 · scoped10.2.6-2
Upgrade ESRI ArcGIS Runtime SDK for Android to version 10.2.6-2 or later to remediate this vulnerability; audit existing applications to identify and rebuild with the patched SDK version.
10.2.6-2 or later
- Identify the current version of ArcGIS Runtime SDK for Android in the project dependencies
- Update the ArcGIS Runtime SDK dependency to version 10.2.6-2 or later in the project's build.gradle or Maven configuration
- Clean and rebuild the project to ensure the new SDK version is properly integrated
- Test the application thoroughly to verify functionality remains intact after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing16.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 $8,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2002 — 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-2002 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