CVE-2024-49732
Google Android 15.0
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-49732 is a high-severity Incorrect Default Permissions (CWE-276) vulnerability in Google Android. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Services File Permissions Weakness (T1574.010); ranked at the 0.1th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-49732 is a vulnerability affecting multiple functions in CompanionDeviceManagerService.java within the Android operating system. It stems from a missing permission check that enables the granting of permissions without user consent, potentially leading to local escalation of privilege. No additional execution privileges are required beyond basic local access, and the issue is rated at a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), linked to CWE-276 (Incorrect Default Permissions). The vulnerability was published on 2025-01-21.
A local attacker with low privileges (PR:L) can exploit this vulnerability with low attack complexity and no user interaction. Successful exploitation allows elevation to higher privileges, resulting in high impacts on confidentiality, integrity, and availability, such as unauthorized access to sensitive data or system resources.
The official Android security bulletin provides mitigation details, available at https://source.android.com/security/bulletin/2025-01-01, which includes patches for affected Android versions.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-43698
Vulnerability Data
In multiple functions of CompanionDeviceManagerService.java, there is a possible way to grant permissions without user consent due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not…
more
needed for exploitation.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 11 hardening rules · 3 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Enforces approved authorizations on files and resources so overly permissive defaults cannot be exploited.
Requires least-privilege defaults so that installed files are not world-writable by default.
Requires documented, restrictive configuration settings that cover file and directory permissions.
Enforces access restrictions on changes, including permission settings applied during installation or configuration.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Hardened baselines and configuration management explicitly require correct default file permissions.
Defining and enforcing least-privilege access permissions directly prevents overly permissive defaults at install time.
Lifecycle management can encompass permission settings, yet the control is too broad to specifically mitigate incorrect defaults.
Secure SDLC practices include establishing secure defaults, but address only the development-phase portion of the weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Standard templates that restrict access to utility programs and host parameter settings prevent the assignment of overly permissive default permissions on critical resources.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Windows Server 2016 (2 rules)
- V-224833 Permissions for program file directories must conform to minimum requirements. prevents CWE-276
- V-224834 Permissions for the Windows installation directory must conform to minimum requirements. prevents CWE-276
Windows Server 2019 (2 rules)
- V-205735 Windows Server 2019 permissions for program file directories must conform to minimum requirements. prevents CWE-276
- V-205736 Windows Server 2019 permissions for the Windows installation directory must conform to minimum requirements. prevents CWE-276
Windows Server 2022 (2 rules)
- V-254252 Windows Server 2022 permissions for program file directories must conform to minimum requirements. prevents CWE-276
- V-254253 Windows Server 2022 permissions for the Windows installation directory must conform to minimum requirements. prevents CWE-276