CVE-2016-2415
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 · uneditedexchange/eas/EasAutoDiscover.java in the Autodiscover implementation in Exchange ActiveSync in Android 5.0.x before 5.0.2, 5.1.x before 5.1.1, and 6.x before 2016-04-01 allows attackers to obtain sensitive information via a crafted application that triggers a spoofed response to a GET request, aka internal bug 26488455.
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 Exchange ActiveSync Autodiscover implementation (exchange/eas/EasAutoDiscover.java) allows a malicious locally-installed application to spoof responses to GET requests, enabling attackers to obtain sensitive configuration information such as Exchange server details.
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.0= 5.0.1= 5.1= 5.1.0= 6.0= 6.0.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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 the Android OS versionGo to Settings > About Phone > Android version (or use 'getprop ro.build.version.release' via ADB)Affected if The installed version is 5.0, 5.0.1, 5.1, 5.1.0, 6.0, or 6.0.1
-
Verify if Exchange ActiveSync is configuredGo to Settings > Accounts > Add Account > Exchange (or check for com.android.exchange in running processes)Affected if An Exchange account is configured and the device synchronizes email via ActiveSync
-
Check for sideloaded or untrusted applicationsReview installed apps in Settings > Apps > Unknown sources enabled, or enumerate installed packages for apps outside the Google Play StoreAffected if The device allows sideloading or has applications installed from untrusted sources
The device is affected if it runs Android 5.0-6.0.1 AND has an Exchange ActiveSync account configured AND permits sideloaded applications that could spoof network responses.
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 dataUpdate affected Android devices to version 5.0.2 or higher for 5.0.x, 5.1.1 or higher for 5.1.x, or the April 2016 security patch level for Android 6.x. Implement application sideloading restrictions to limit exposure to malicious apps.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.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 $3,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-2415 — 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-2016-2415 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