First published: Tue Nov 07 2023(Updated: )
An improper input validation in saped_dec in libsaped prior to SMR Nov-2023 Release 1 allows local attackers to cause out-of-bounds read and write.
Credit: mobile.security@samsung.com
Affected Software | Affected Version | How to fix |
---|---|---|
Samsung Android | =11.0 | |
Samsung Android | =11.0-smr-apr-2021-r1 | |
Samsung Android | =11.0-smr-apr-2022-r1 | |
Samsung Android | =11.0-smr-apr-2023-r1 | |
Samsung Android | =11.0-smr-aug-2021-r1 | |
Samsung Android | =11.0-smr-aug-2022-r1 | |
Samsung Android | =11.0-smr-aug-2023-r1 | |
Samsung Android | =11.0-smr-dec-2020-r1 | |
Samsung Android | =11.0-smr-dec-2021-r1 | |
Samsung Android | =11.0-smr-dec-2022-r1 | |
Samsung Android | =11.0-smr-feb-2021-r1 | |
Samsung Android | =11.0-smr-feb-2022-r1 | |
Samsung Android | =11.0-smr-feb-2023-r1 | |
Samsung Android | =11.0-smr-jan-2021-r1 | |
Samsung Android | =11.0-smr-jan-2022-r1 | |
Samsung Android | =11.0-smr-jan-2023-r1 | |
Samsung Android | =11.0-smr-jul-2021-r1 | |
Samsung Android | =11.0-smr-jul-2022-r1 | |
Samsung Android | =11.0-smr-jul-2023-r1 | |
Samsung Android | =11.0-smr-jun-2021-r1 | |
Samsung Android | =11.0-smr-jun-2022-r1 | |
Samsung Android | =11.0-smr-jun-2023-r1 | |
Samsung Android | =11.0-smr-mar-2021-r1 | |
Samsung Android | =11.0-smr-mar-2022-r1 | |
Samsung Android | =11.0-smr-mar-2023-r1 | |
Samsung Android | =11.0-smr-may-2021-r1 | |
Samsung Android | =11.0-smr-may-2022-r1 | |
Samsung Android | =11.0-smr-may-2023-r1 | |
Samsung Android | =11.0-smr-nov-2021-r1 | |
Samsung Android | =11.0-smr-nov-2022-r1 | |
Samsung Android | =11.0-smr-oct-2021-r1 | |
Samsung Android | =11.0-smr-oct-2022-r1 | |
Samsung Android | =11.0-smr-oct-2023-r1 | |
Samsung Android | =11.0-smr-sep-2021-r1 | |
Samsung Android | =11.0-smr-sep-2022-r1 | |
Samsung Android | =11.0-smr-sep-2023-r1 | |
Samsung Android | =12.0 | |
Samsung Android | =12.0-smr-apr-2022-r1 | |
Samsung Android | =12.0-smr-apr-2023-r1 | |
Samsung Android | =12.0-smr-aug-2022-r1 | |
Samsung Android | =12.0-smr-aug-2023-r1 | |
Samsung Android | =12.0-smr-dec-2021-r1 | |
Samsung Android | =12.0-smr-dec-2022-r1 | |
Samsung Android | =12.0-smr-feb-2022-r1 | |
Samsung Android | =12.0-smr-feb-2023-r1 | |
Samsung Android | =12.0-smr-jan-2022-r1 | |
Samsung Android | =12.0-smr-jan-2023-r1 | |
Samsung Android | =12.0-smr-jul-2022-r1 | |
Samsung Android | =12.0-smr-jul-2023-r1 | |
Samsung Android | =12.0-smr-jun-2022-r1 | |
Samsung Android | =12.0-smr-jun-2023-r1 | |
Samsung Android | =12.0-smr-mar-2022-r1 | |
Samsung Android | =12.0-smr-mar-2023-r1 | |
Samsung Android | =12.0-smr-may-2022-r1 | |
Samsung Android | =12.0-smr-may-2023-r1 | |
Samsung Android | =12.0-smr-nov-2021-r1 | |
Samsung Android | =12.0-smr-nov-2022-r1 | |
Samsung Android | =12.0-smr-oct-2022-r1 | |
Samsung Android | =12.0-smr-oct-2023-r1 | |
Samsung Android | =12.0-smr-sep-2022-r1 | |
Samsung Android | =12.0-smr-sep-2023-r1 | |
Samsung Android | =13.0 | |
Samsung Android | =13.0-smr-apr-2023-r1 | |
Samsung Android | =13.0-smr-aug-2023-r1 | |
Samsung Android | =13.0-smr-dec-2022-r1 | |
Samsung Android | =13.0-smr-feb-2023-r1 | |
Samsung Android | =13.0-smr-jan-2023-r1 | |
Samsung Android | =13.0-smr-jul-2023-r1 | |
Samsung Android | =13.0-smr-jun-2023-r1 | |
Samsung Android | =13.0-smr-mar-2023-r1 | |
Samsung Android | =13.0-smr-may-2023-r1 | |
Samsung Android | =13.0-smr-nov-2022-r1 | |
Samsung Android | =13.0-smr-oct-2022-r1 | |
Samsung Android | =13.0-smr-oct-2023-r1 | |
Samsung Android | =13.0-smr-sep-2023-r1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2023-42536 is classified as critical, due to its potential for causing out-of-bounds read and write vulnerabilities.
To fix CVE-2023-42536, update to the latest versions of Samsung Android specified in the security release notes.
CVE-2023-42536 affects users running specific versions of Samsung Android 11.0 and Android 12.0 prior to SMR Nov-2023 Release 1.
CVE-2023-42536 exploits improper input validation leading to potential out-of-bounds read and write access.
No, CVE-2023-42536 requires local access for exploitation, making it a local attack vector.