A Type Confusion vulnerability was found in the Spotlight RPC functions in afpd in Netatalk 3.1.x before 3.1.17. When parsing Spotlight RPC packets, one encoded data structure is a key-value style dictionary where the keys are character strings, and the values can be any of the supported types in the underlying protocol. Due to a lack of type checking in callers of the dalloc_value_for_key() function, which returns the object associated with a key, a malicious actor may be able to fully control the value of the pointer and theoretically achieve Remote Code Execution on the host. This issue is similar to CVE-2023-34967.
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 |
|---|---|---|---|
| Netatalk | Netatalk | 3.1 (including) | 3.1.17 (excluding) |
| Netatalk | Ubuntu | esm-apps/noble | * |
| Netatalk | Ubuntu | focal | * |
| Netatalk | Ubuntu | jammy | * |
| Netatalk | Ubuntu | lunar | * |
| Netatalk | Ubuntu | mantic | * |
| Netatalk | Ubuntu | noble | * |
| Netatalk | Ubuntu | upstream | * |
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.