First published: Tue Nov 07 2023(Updated: )
Improper Certificate Validation in FotaAgent prior to SMR Nov-2023 Release1 allows remote attacker to intercept the network traffic including Firmware information.
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.
CVE-2023-42532 is classified as a critical vulnerability due to its potential to allow remote attackers to intercept sensitive data.
To address CVE-2023-42532, users should update to the latest firmware version available from Samsung.
CVE-2023-42532 affects multiple versions of Samsung Android, including 11.0, 12.0, and 13.0 prior to the SMR Nov-2023 Release1.
Yes, CVE-2023-42532 can potentially lead to data breaches by allowing attackers to intercept firmware and network traffic.
Currently, the only effective workaround for CVE-2023-42532 is to promptly update your device to the latest software version.