# CVE-2014-8610: Missing authorization in n/a

> Attackers can send stored SMS messages and incur charges by exploiting a missing permission check in the Android SMS receiver.

- **Severity:** Low 3.3 (`AV:L/AC:M/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-chjx-6gcx-3j5v

## What is CVE-2014-8610?

CVE-2014-8610 is a low-severity missing authorization vulnerability in Google Android, published on 15 Dec 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-264

## Which versions are affected by CVE-2014-8610?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2014-8610?

No fix has been published for CVE-2014-8610 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-8610 being exploited?

There is no known exploitation of CVE-2014-8610 in the wild and no public exploit code.

Public exploit code:

- Educational Proof-of-Concept for the Dual_EC_DRBG backdoor (CVE-2014-8610) - NIST P-256 state recovery attack demonstration (github_poc): https://github.com/eddieoz/dual-ec-drbg

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-8610 and fix it if it is affected.

What it is: CVE-2014-8610 is a low-severity missing authorization vulnerability in Google Android, published on 15 Dec 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-8610 in the wild and no public exploit code.

Affected product: Google Android. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-8610/ (Markdown: https://insights.sbomify.com/CVE-2014-8610/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-8610
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-8610
- OSV: https://osv.dev/vulnerability/CVE-2014-8610

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-8610/
Summaries are generated and may contain mistakes; the official description above is the record.