There is a vulnerability of accessing resources using an incompatible type (type confusion) in the Bastet module. Successful exploitation of this vulnerability may affect integrity.
The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Emui | Huawei | 10.1.0 (including) | 10.1.0 (including) |
| Emui | Huawei | 10.1.1 (including) | 10.1.1 (including) |
| Emui | Huawei | 11.0.0 (including) | 11.0.0 (including) |
| Emui | Huawei | 11.0.1 (including) | 11.0.1 (including) |
| Emui | Huawei | 12.0.0 (including) | 12.0.0 (including) |
| Harmonyos | Huawei | 2.0 (including) | 2.0 (including) |
| Magic_ui | Huawei | 3.1.0 (including) | 3.1.0 (including) |
| Magic_ui | Huawei | 3.1.1 (including) | 3.1.1 (including) |
| Magic_ui | Huawei | 4.0.0 (including) | 4.0.0 (including) |
When the product accesses the resource using an incompatible type, this could trigger logical errors because the resource does not have expected properties. In languages without memory safety, such as C and C++, type confusion can lead to out-of-bounds memory access. While this weakness is frequently associated with unions when parsing data with many different embedded object types in C, it can be present in any application that can interpret the same variable or memory location in multiple ways. This weakness is not unique to C and C++. For example, errors in PHP applications can be triggered by providing array parameters when scalars are expected, or vice versa. Languages such as Perl, which perform automatic conversion of a variable of one type when it is accessed as if it were another type, can also contain these issues.