CVE-2017-0394
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 · uneditedA denial of service vulnerability in Telephony could enable a remote attacker to cause a device hang or reboot. This issue is rated as High due to the possibility of remote denial of service. Product: Android. Versions: 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1. Android ID: A-31752213.
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 · moderate confidenceA remote denial of service vulnerability exists in the Android Telephony component that allows an attacker to cause affected devices to hang or forcibly reboot. The vulnerability is exploitable remotely, likely through malformed telephony-related network communications (such as SMS, MMS, or IMS signaling), and affects multiple Android versions from 5.0.2 through 7.1.
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.0.2= 5.1= 5.1.0= 5.1.1= 6.0= 6.0.1= 7.0= 7.1.0CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Check Android OS versionGo to Settings > About Phone > Android version, or run 'adb shell getprop ro.build.version.release'Affected if Version is 5.0, 5.0.1, 5.0.2, 5.1, 5.1.0, 5.1.1, 6.0, 6.0.1, 7.0, or 7.1.0
-
Confirm telephony service is activeCheck that the device has cellular calling capability enabled - verify TelephonyManager is present by running 'adb shell pm list packages | grep telephony' or check that Phone app is installed and SIM is activeAffected if Device has functional telephony (SIM card active and phone service enabled) AND runs a vulnerable Android version
-
Verify SMS/MMS/IMS messaging is enabledCheck that default SMS app is configured in Settings > Apps > Default apps > SMS, or run 'adb shell content query --uri content://sms/ --projection _id' to confirm SMS database is accessibleAffected if SMS, MMS, or IMS messaging services are enabled and the Android version is in the affected list
The device is affected if it runs Android version 5.0 through 7.1.0 and has an active SIM card with telephony or messaging services enabled, as the vulnerability can be triggered remotely via malformed telephony network communications.
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 applicable Android security patch (January 2017 Security Bulletin or later) to all affected devices. For enterprise deployments, ensure mobile device management (MDM) systems are configured to enforce and verify timely security updates.
- Consultation4.0 h
- Implementation8.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-0394 — 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-2017-0394 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