First published: Wed Nov 06 2024(Updated: )
Improper input validation in Settings Suggestions prior to SMR Nov-2024 Release 1 allows local attackers to launch privileged activities.
Credit: mobile.security@samsung.com
Affected Software | Affected Version | How to fix |
---|---|---|
Samsung Android | =13.0 | |
Samsung Android | =13.0-smr-apr-2022-r1 | |
Samsung Android | =13.0-smr-apr-2023-r1 | |
Samsung Android | =13.0-smr-apr-2024-r1 | |
Samsung Android | =13.0-smr-aug-2022-r1 | |
Samsung Android | =13.0-smr-aug-2023-r1 | |
Samsung Android | =13.0-smr-aug-2024-r1 | |
Samsung Android | =13.0-smr-dec-2021-r1 | |
Samsung Android | =13.0-smr-dec-2022-r1 | |
Samsung Android | =13.0-smr-dec-2023-r1 | |
Samsung Android | =13.0-smr-feb-2022-r1 | |
Samsung Android | =13.0-smr-feb-2023-r1 | |
Samsung Android | =13.0-smr-feb-2024-r1 | |
Samsung Android | =13.0-smr-jan-2022-r1 | |
Samsung Android | =13.0-smr-jan-2023-r1 | |
Samsung Android | =13.0-smr-jan-2024-r1 | |
Samsung Android | =13.0-smr-jul-2022-r1 | |
Samsung Android | =13.0-smr-jul-2023-r1 | |
Samsung Android | =13.0-smr-jul-2024-r1 | |
Samsung Android | =13.0-smr-jun-2022-r1 | |
Samsung Android | =13.0-smr-jun-2023-r1 | |
Samsung Android | =13.0-smr-jun-2024-r1 | |
Samsung Android | =13.0-smr-mar-2022-r1 | |
Samsung Android | =13.0-smr-mar-2023-r1 | |
Samsung Android | =13.0-smr-mar-2024-r1 | |
Samsung Android | =13.0-smr-may-2022-r1 | |
Samsung Android | =13.0-smr-may-2023-r1 | |
Samsung Android | =13.0-smr-may-2024-r1 | |
Samsung Android | =13.0-smr-nov-2021-r1 | |
Samsung Android | =13.0-smr-nov-2022-r1 | |
Samsung Android | =13.0-smr-nov-2023-r1 | |
Samsung Android | =13.0-smr-oct-2022-r1 | |
Samsung Android | =13.0-smr-oct-2023-r1 | |
Samsung Android | =13.0-smr-oct-2024-r1 | |
Samsung Android | =13.0-smr-sep-2022-r1 | |
Samsung Android | =13.0-smr-sep-2023-r1 | |
Samsung Android | =13.0-smr-sep-2024-r1 | |
Samsung Android | =14.0 | |
Samsung Android | =14.0-smr-apr-2022-r1 | |
Samsung Android | =14.0-smr-apr-2023-r1 | |
Samsung Android | =14.0-smr-apr-2024-r1 | |
Samsung Android | =14.0-smr-aug-2022-r1 | |
Samsung Android | =14.0-smr-aug-2023-r1 | |
Samsung Android | =14.0-smr-aug-2024-r1 | |
Samsung Android | =14.0-smr-dec-2021-r1 | |
Samsung Android | =14.0-smr-dec-2022-r1 | |
Samsung Android | =14.0-smr-dec-2023-r1 | |
Samsung Android | =14.0-smr-feb-2022-r1 | |
Samsung Android | =14.0-smr-feb-2023-r1 | |
Samsung Android | =14.0-smr-feb-2024-r1 | |
Samsung Android | =14.0-smr-jan-2022-r1 | |
Samsung Android | =14.0-smr-jan-2023-r1 | |
Samsung Android | =14.0-smr-jan-2024-r1 | |
Samsung Android | =14.0-smr-jul-2022-r1 | |
Samsung Android | =14.0-smr-jul-2023-r1 | |
Samsung Android | =14.0-smr-jul-2024-r1 | |
Samsung Android | =14.0-smr-jun-2022-r1 | |
Samsung Android | =14.0-smr-jun-2023-r1 | |
Samsung Android | =14.0-smr-jun-2024-r1 | |
Samsung Android | =14.0-smr-mar-2022-r1 | |
Samsung Android | =14.0-smr-mar-2023-r1 | |
Samsung Android | =14.0-smr-mar-2024-r1 | |
Samsung Android | =14.0-smr-may-2022-r1 | |
Samsung Android | =14.0-smr-may-2023-r1 | |
Samsung Android | =14.0-smr-may-2024-r1 | |
Samsung Android | =14.0-smr-nov-2021-r1 | |
Samsung Android | =14.0-smr-nov-2022-r1 | |
Samsung Android | =14.0-smr-nov-2023-r1 | |
Samsung Android | =14.0-smr-oct-2022-r1 | |
Samsung Android | =14.0-smr-oct-2023-r1 | |
Samsung Android | =14.0-smr-oct-2024-r1 | |
Samsung Android | =14.0-smr-sep-2022-r1 | |
Samsung Android | =14.0-smr-sep-2023-r1 | |
Samsung Android | =14.0-smr-sep-2024-r1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-49401 has been classified as a high severity vulnerability due to its potential for exploitation by local attackers.
To mitigate CVE-2024-49401, it is recommended to update your Samsung Android device to the latest software version available.
CVE-2024-49401 affects several versions of Samsung Android 13.0 and 14.0, specifically those released before the SMR Nov-2024 Release 1.
Yes, CVE-2024-49401 allows local attackers to launch privileged activities, potentially leading to unauthorized access.
Currently, there is no known workaround for CVE-2024-49401 besides applying the appropriate software update as soon as possible.