Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-12080: CWE-345 Insufficient Verification of Data Authenticity in Google WearOS

0
Medium
VulnerabilityCVE-2025-12080cvecve-2025-12080cwe-345
Published: Mon Oct 27 2025 (10/27/2025, 08:45:52 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: WearOS

Description

On Wear OS devices, when Google Messages is configured as the default SMS/MMS/RCS application, the handling of ACTION_SENDTO intents utilizing the sms:, smsto:, mms:, and mmsto: Uniform Resource Identifier (URI) schemes is incorrectly implemented. Due to this misconfiguration, an attacker capable of invoking an Android intent can exploit this vulnerability to send messages on the user’s behalf to arbitrary receivers without requiring any further user interaction or specific permissions. This allows for the silent and unauthorized transmission of messages from a compromised Wear OS device.

AI-Powered Analysis

AILast updated: 11/03/2025, 09:25:59 UTC

Technical Analysis

CVE-2025-12080 is a vulnerability identified in Google Wear OS devices when Google Messages is configured as the default SMS/MMS/RCS application. The issue stems from incorrect implementation in handling ACTION_SENDTO intents that use sms:, smsto:, mms:, and mmsto: URI schemes. Specifically, the system fails to properly verify the authenticity of data within these intents, classified under CWE-345 (Insufficient Verification of Data Authenticity). An attacker capable of invoking Android intents on the device can exploit this flaw to send SMS or MMS messages silently and without requiring any user interaction or special permissions. This means that if an attacker gains the ability to trigger intents—potentially through a compromised app or other means—they can cause the device to send messages to arbitrary recipients without the user's knowledge. The vulnerability does not require prior authentication or elevated privileges, and no user interface prompts are necessary, which increases the stealthiness of the attack. The CVSS 4.0 base score is 6.9 (medium severity), reflecting the attack vector as adjacent network (AV:A), low attack complexity, no privileges required, but user interaction is required to initiate the intent invocation. The impact primarily affects message integrity and confidentiality, as unauthorized messages can be sent, potentially leading to information leakage, fraud, or social engineering attacks. Currently, there are no known exploits in the wild, and no official patches have been released. The vulnerability was published on October 27, 2025, and remains unpatched, requiring vigilance from users and administrators. This vulnerability highlights the risks associated with intent handling in Android-based wearable devices and the importance of strict verification of data authenticity in inter-process communication.

Potential Impact

For European organizations, this vulnerability poses risks primarily to the confidentiality and integrity of communications on Wear OS devices. Unauthorized message sending can lead to data leakage, phishing, or social engineering attacks targeting employees or customers. Organizations relying on Wear OS devices for critical communications or two-factor authentication via SMS may face increased risk of account compromise or fraud. The silent nature of the exploit means users may remain unaware of the compromise, complicating incident detection and response. Additionally, misuse of messaging services could result in reputational damage or financial losses if attackers send fraudulent messages impersonating the organization. The impact is heightened in sectors with stringent data protection requirements, such as finance, healthcare, and government, where unauthorized message transmission could violate regulatory compliance. However, the requirement for the attacker to invoke intents on the device limits remote exploitation, suggesting that initial device compromise or physical access is likely needed. This reduces the broad impact but still represents a significant threat to endpoint security within organizations using Wear OS devices.

Mitigation Recommendations

1. Restrict which applications can invoke intents on Wear OS devices by enforcing strict app permissions and intent filters, minimizing exposure to malicious apps capable of triggering ACTION_SENDTO intents. 2. Monitor device logs and messaging activity for unusual or unauthorized message sending patterns, enabling early detection of exploitation attempts. 3. Educate users about the risks of installing untrusted applications or granting excessive permissions that could facilitate intent invocation by attackers. 4. Implement endpoint protection solutions that can detect anomalous intent invocations or suspicious inter-process communications on Wear OS devices. 5. Apply security updates and patches promptly once Google releases a fix for this vulnerability. 6. Consider disabling or limiting the use of Google Messages as the default SMS/MMS/RCS app on Wear OS devices in high-risk environments until the vulnerability is addressed. 7. Use mobile device management (MDM) solutions to enforce security policies and restrict app installations and configurations on Wear OS devices within the organization. 8. For critical communications, use alternative secure messaging platforms that do not rely on vulnerable intent handling mechanisms.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Google
Date Reserved
2025-10-22T15:24:43.272Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68ff324b8f87cfec3dea7cb6

Added to database: 10/27/2025, 8:50:19 AM

Last enriched: 11/3/2025, 9:25:59 AM

Last updated: 12/14/2025, 4:34:44 PM

Views: 299

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats