LiveActive security incident?Get immediate response
CVE Record

CVE-2014-8610: AndroidManifest.xml in Android before 5.0.0 does not require the SEND_SMS permission for the SmsReceiver re...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Android versions before 5.0 allowed a malicious app to abuse the MMS/SMS component to send stored or draft SMS messages without the normal SEND_SMS permission. Business impact is mainly unexpected SMS charges, user trust loss, and potential misuse of managed legacy devices, not broad server compromise. Exposure is limited to Android devices running versions before 5.0.0 with the vulnerable Mms component. Modern supported Android fleets should generally be unaffected, but unmanaged, embedded, kiosk, or legacy BYOD devices may still matter. Treat this as a legacy mobile hygiene issue. Prioritize if the organization still operates Android 4.x devices with SMS capability, especially shared, kiosk, field, or unmanaged devices. For modern Android fleets, urgency is lower. Mitigation focus: Inventory managed Android devices and identify any versions before 5.0.0.; Upgrade affected devices to Android 5.0.0 or later where feasible.; Confirm vendor firmware includes the Android Mms Bug 17671795 fix..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2014-8610 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.