Skip to main content

CVE-2024-56193: Information disclosure in Google Android

Medium
VulnerabilityCVE-2024-56193cvecve-2024-56193
Published: Tue May 27 2025 (05/27/2025, 15:41:27 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Android

Description

There is a possible disclosure of Bluetooth adapter details due to a permissions bypass. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

AI-Powered Analysis

AILast updated: 07/06/2025, 00:57:03 UTC

Technical Analysis

CVE-2024-56193 is a medium-severity vulnerability affecting the Android kernel, specifically related to the Bluetooth subsystem. The vulnerability arises from a permissions bypass that allows an attacker to disclose details about the Bluetooth adapter without requiring any additional execution privileges or user interaction. This means that a local attacker with access to the device can retrieve sensitive information about the Bluetooth adapter, such as its configuration or state, which is normally protected by permissions. The vulnerability is categorized under CWE-200 (Information Exposure), indicating that it leaks information that could aid an attacker in further exploitation or reconnaissance. The CVSS 3.1 base score is 5.1, reflecting a medium impact with low attack complexity, no privileges required, and no user interaction needed. The scope is unchanged, and the impact affects confidentiality and integrity to a limited extent, with no impact on availability. No known exploits are currently reported in the wild, and no patches have been linked yet. The vulnerability affects the Android kernel, which is widely deployed across numerous devices globally, including smartphones, tablets, and embedded systems running Android OS. Since the flaw is local and requires no user interaction, it could be exploited by malicious apps or local attackers who gain physical or logical access to the device, potentially enabling them to gather Bluetooth adapter information that might facilitate further attacks or privacy violations.

Potential Impact

For European organizations, this vulnerability poses a moderate risk primarily in environments where Android devices are used extensively, such as in mobile workforces, BYOD scenarios, or IoT deployments. The information disclosure could aid attackers in profiling devices or crafting targeted Bluetooth-based attacks, potentially leading to further compromise or data leakage. While the immediate impact is limited to information disclosure, the leaked Bluetooth adapter details could be leveraged to bypass security controls or exploit other vulnerabilities in the Bluetooth stack. This is particularly relevant for sectors with high reliance on mobile communications and Bluetooth peripherals, such as finance, healthcare, and critical infrastructure. Additionally, organizations subject to stringent data protection regulations like GDPR must consider the privacy implications of such leaks, as unauthorized disclosure of device information could be viewed as a data breach. The lack of user interaction and privileges required increases the risk of stealthy exploitation, especially in environments where device physical security is limited or where malicious applications can be installed.

Mitigation Recommendations

To mitigate CVE-2024-56193, European organizations should prioritize the following actions: 1) Ensure all Android devices are updated promptly once official patches become available from device manufacturers or Google. 2) Implement strict application control policies to limit installation of untrusted or unnecessary apps that could exploit local vulnerabilities. 3) Employ mobile device management (MDM) solutions to enforce security configurations, including restricting Bluetooth usage or access to Bluetooth adapter information where feasible. 4) Monitor device behavior for unusual Bluetooth activity or unauthorized access attempts. 5) Educate users about the risks of installing apps from unknown sources and the importance of device security hygiene. 6) For critical environments, consider disabling Bluetooth functionality on devices where it is not required to reduce the attack surface. 7) Collaborate with vendors to obtain timely security updates and verify patch deployment status across the device fleet. These measures go beyond generic advice by focusing on controlling local access, application permissions, and device configurations specific to Bluetooth usage.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Google_Devices
Date Reserved
2024-12-18T17:17:02.550Z
Cvss Version
null
State
PUBLISHED

Threat ID: 6835e152182aa0cae218e504

Added to database: 5/27/2025, 3:59:14 PM

Last enriched: 7/6/2025, 12:57:03 AM

Last updated: 8/12/2025, 12:16:04 PM

Views: 19

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

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