CVE-2014-8610
Last modified
CVE-2014-8610 is a vulnerability of currently unknown severity. AndroidManifest.xml in Android before 5.0.0 does not require the SEND_SMS permission for the SmsReceiver receiver, which allows attackers to send stored SMS messages, and consequently transmit arbitrary new draft SMS messages or trigger additional per-message charges from a network operator for old messages, via a crafted application that broadcasts an intent with the com.android.mms.transaction.MESSAGE_SENT action, aka Bug 17671795.. EPSS estimates a 0.34% chance of exploitation in the next 30 days.
Description
AndroidManifest.xml in Android before 5.0.0 does not require the SEND_SMS permission for the SmsReceiver receiver, which allows attackers to send stored SMS messages, and consequently transmit arbitrary new draft SMS messages or trigger additional per-message charges from a network operator for old messages, via a crafted application that broadcasts an intent with the com.android.mms.transaction.MESSAGE_SENT action, aka Bug 17671795.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Android | <= 4.4.4 | |
| Android | 1.0 | |
| Android | 1.1 | |
| Android | 1.5 | |
| Android | 1.6 | |
| Android | 2.0 | |
| Android | 2.0.1 | |
| Android | 2.1 | |
| Android | 2.2 | |
| Android | 2.2.1 | |
| Android | 2.2.2 | |
| Android | 2.2.3 | |
| Android | 2.3 | |
| Android | 2.3.1 | |
| Android | 2.3.2 | |
| Android | 2.3.3 | |
| Android | 2.3.4 | |
| Android | 2.3.5 | |
| Android | 2.3.6 | |
| Android | 2.3.7 | |
| Android | 3.0 | |
| Android | 3.1 | |
| Android | 3.2 | |
| Android | 3.2.1 | |
| Android | 3.2.2 | |
| Android | 3.2.4 | |
| Android | 3.2.6 | |
| Android | 4.0 | |
| Android | 4.0.1 | |
| Android | 4.0.2 | |
| Android | 4.0.3 | |
| Android | 4.0.4 | |
| Android | 4.1 | |
| Android | 4.1.2 | |
| Android | 4.2 | |
| Android | 4.2.1 | |
| Android | 4.2.2 | |
| Android | 4.3 | |
| Android | 4.3.1 | |
| Android | 4.4 | |
| Android | 4.4.1 | |
| Android | 4.4.2 | |
| Android | 4.4.3 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2014-8610?
How severe is CVE-2014-8610?
How do I fix CVE-2014-8610?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2014
- CVE-2014-8604The XCloner plugin 3.1.1 for WordPress and 3.5.1 for Joomla!…
- CVE-2014-8605The XCloner plugin 3.1.1 for WordPress and 3.5.1 for Joomla!…
- CVE-2014-8606Directory traversal vulnerability in the XCloner plugin 3.1.…
- CVE-2014-8607The XCloner plugin 3.1.1 for WordPress and 3.5.1 for Joomla!…
- CVE-2014-8608The K7Sentry.sys kernel mode driver (aka K7AV Sentry Device …
- CVE-2014-8609The addAccount method in src/com/android/settings/accounts/A…
- CVE-2014-8611The __sflush function in fflush.c in stdio in libc in FreeBS…
- CVE-2014-8612Multiple array index errors in the Stream Control Transmissi…
- CVE-2014-8613The sctp module in FreeBSD 10.1 before p5, 10.0 before p17, …
- CVE-2014-8614Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultI…
- CVE-2014-8615Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultI…
- CVE-2014-8616Multiple cross-site scripting (XSS) vulnerabilities in Forti…
Are you affected by CVE-2014-8610?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
