Samsung Devices DeviceIdService intent by broadcast receiver

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.3$0-$5k0.00

Summaryinfo

A vulnerability was found in Samsung Devices. It has been rated as problematic. Affected by this issue is some unknown functionality of the component DeviceIdService. The manipulation leads to intent by broadcast receiver. This vulnerability is documented as CVE-2025-20942. The attack needs to be performed locally. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Samsung Devices (version unknown). It has been rated as problematic. This issue affects an unknown function of the component DeviceIdService. The manipulation with an unknown input leads to a intent by broadcast receiver vulnerability. Using CWE to declare the problem leads to CWE-925. The Android application uses a Broadcast Receiver that receives an Intent but does not properly verify that the Intent came from an authorized source. Impacted is integrity, and availability. The summary by CVE is:

Improper Verification of Intent by Broadcast Receiver in DeviceIdService prior to SMR Apr-2025 Release 1 allows local attackers to reset OAID.

The advisory is shared at security.samsungmobile.com. The identification of this vulnerability is CVE-2025-20942 since 11/06/2024. The exploitation is known to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available.

Upgrading eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2025-0726). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Samsung Android

Productinfo

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.4
VulDB Meta Temp Score: 4.3

VulDB Base Score: 4.4
VulDB Temp Score: 4.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 4.4
CNA Vector (SamsungMobile): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Intent by broadcast receiver
CWE: CWE-925
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Timelineinfo

11/06/2024 🔍
04/08/2025 +152 days 🔍
04/08/2025 +0 days 🔍
11/10/2025 +216 days 🔍

Sourcesinfo

Vendor: samsung.com

Advisory: security.samsungmobile.com
Status: Confirmed

CVE: CVE-2025-20942 (🔍)
GCVE (CVE): GCVE-0-2025-20942
GCVE (VulDB): GCVE-100-303821
CERT Bund: WID-SEC-2025-0726 - Samsung Android: Mehrere Schwachstellen

Entryinfo

Created: 04/08/2025 12:49
Updated: 11/10/2025 13:38
Changes: 04/08/2025 12:49 (61), 04/08/2025 15:39 (1), 11/10/2025 13:38 (6)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!