CVE-2023-41829
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-41829 is a medium-severity Improper Export of Android Application Components (CWE-926) vulnerability in Motorola Carrier Services (inferred from references). Its CVSS base score is 5.0 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 4th 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.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-46321
Vulnerability Data
An improper export vulnerability was reported in the Motorola Carrier Services application that could allow a malicious, local application to read files without authorization.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
AC-3 directly requires enforcement of authorizations on logical access, which stops an exported Android component from being reachable without proper restrictions.
Least privilege reduces the exposure of exported components by limiting unnecessary authorizations granted to other apps.
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.
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.
A.8.26 only requires that security requirements (including access segregation) be identified and specified during development; it does not itself enforce, implement or configure the restrictions that would stop an improperly-exported Android component from being launched or accessed by unauthorized apps.
A.8.27 mandates security-by-design principles (least privilege, default-deny, distrust external input, zero-trust verification) and design reviews that can stop unsafe component export decisions, but this is only one slice of the weakness class; many export flaws arise from concrete permission/Intent-filter misconfigurations that the high-level principles and reviews do not themselves enforce.
Secure-coding standards require explicit permission declarations and intent-filter restrictions to avoid improper exports.
Security testing can detect exported components lacking proper restrictions, providing partial coverage of the weakness.
Enforcing information-access restrictions on exported Android components directly prevents unauthorized launch or data access.