Samsung S Assistant up to 9.3.1 intent by broadcast receiver
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Samsung S Assistant up to 9.3.1. The affected element is an unknown function. Executing a manipulation can lead to intent by broadcast receiver. This vulnerability is handled as CVE-2025-21040. It is possible to launch the attack on the local host. There is not any exploit available. Upgrading the affected component is recommended.
Details
A vulnerability was found in Samsung S Assistant up to 9.3.1. It has been declared as problematic. This vulnerability affects an unknown code block. The manipulation with an unknown input leads to a intent by broadcast receiver vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect integrity, and availability. CVE summarizes:
Improper verification of intent by ExternalBroadcastReceiver in S Assistant prior to version 9.3.2 allows local attackers to modify itinerary information.
The advisory is available at security.samsungmobile.com. This vulnerability was named CVE-2025-21040 since 11/06/2024. The exploitation appears to be easy. Local access is required to approach this attack. The technical details are unknown and an exploit is not available.
Upgrading to version 9.3.2 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.samsung.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.4
VulDB Temp Score: 4.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 3.3
NVD Vector: 🔒
CNA Base Score: 5.1
CNA Vector (SamsungMobile): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Intent by broadcast receiverCWE: 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-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: S Assistant 9.3.2
Timeline
11/06/2024 CVE reserved09/03/2025 Advisory disclosed
09/03/2025 VulDB entry created
09/06/2025 VulDB entry last update
Sources
Vendor: samsung.comAdvisory: security.samsungmobile.com
Status: Confirmed
CVE: CVE-2025-21040 (🔒)
GCVE (CVE): GCVE-0-2025-21040
GCVE (VulDB): GCVE-100-322306
Entry
Created: 09/03/2025 10:12Updated: 09/06/2025 00:09
Changes: 09/03/2025 10:12 (62), 09/06/2025 00:09 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.