First published: Thu Jul 06 2023(Updated: )
Heap out of bound write vulnerability in IpcRxUsimPhoneBookCapa of RILD prior to SMR Jul-2023 Release 1 allows attackers to execute arbitrary code.
Credit: mobile.security@samsung.com
Affected Software | Affected Version | How to fix |
---|---|---|
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-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-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-2022-r1 | |
Samsung Android | =11.0-smr-nov-2023-r1 | |
Samsung Android | =11.0-smr-oct-2021-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 | =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-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-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-sep-2022-r1 | |
Samsung Android | =13.0-smr-apr-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-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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-30647 is considered a critical vulnerability due to its ability to allow attackers to execute arbitrary code.
To fix CVE-2023-30647, users should update to the latest Samsung Android software version released after the SMR Jul-2023.
CVE-2023-30647 affects various Samsung Android devices running versions up to SMR Jul-2023 Release 1.
The potential impacts of CVE-2023-30647 include unauthorized access, data theft, or device control.
As of now, there are no specific public exploits for CVE-2023-30647, but its critical nature means it could be targeted.