Motorola Framework prior 2023-09-01 Telephony implicit intent

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.
2.7$0-$5k0.00

Summaryinfo

A vulnerability has been found in Motorola Framework and classified as problematic. Impacted is an unknown function of the component Telephony Handler. This manipulation causes implicit intent. This vulnerability appears as CVE-2024-3480. The attack requires local access. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability has been found in Motorola Framework and classified as problematic. Affected by this vulnerability is an unknown part of the component Telephony Handler. The manipulation with an unknown input leads to a implicit intent vulnerability. The CWE definition for the vulnerability is CWE-927. The Android application uses an implicit intent for transmitting sensitive data to other applications. As an impact it is known to affect confidentiality. The summary by CVE is:

An Implicit intent vulnerability was reported in the Motorola framework that could allow an attacker to read telephony-related data.

The weakness was presented by Sergey Toshin and Illia Khorolskyi. The advisory is shared at en-us.support.motorola.com. This vulnerability is known as CVE-2024-3480 since 04/08/2024. The exploitation appears to be easy. An attack has to be approached locally. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.

Upgrading to version 2023-09-01 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

Name

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 2.8
VulDB Meta Temp Score: 2.7

VulDB Base Score: 2.8
VulDB Temp Score: 2.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 2.8
CNA Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Implicit intent
CWE: CWE-927
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Partially

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: 🔍

Upgrade: Framework 2023-09-01

Timelineinfo

09/01/2023 🔍
04/08/2024 +220 days 🔍
05/03/2024 +25 days 🔍
05/03/2024 +0 days 🔍
04/01/2025 +333 days 🔍

Sourcesinfo

Advisory: en-us.support.motorola.com
Researcher: Sergey Toshin, Illia Khorolskyi
Status: Confirmed

CVE: CVE-2024-3480 (🔍)
GCVE (CVE): GCVE-0-2024-3480
GCVE (VulDB): GCVE-100-262993

Entryinfo

Created: 05/03/2024 17:06
Updated: 04/01/2025 14:58
Changes: 05/03/2024 17:06 (63), 04/01/2025 14:58 (4)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Might our Artificial Intelligence support you?

Check our Alexa App!