The RPC library in Kerberos 5 1.4 through 1.4.4, and 1.5 through 1.5.1, as used in Kerberos administration daemon (kadmind) and other products that use this library, calls an uninitialized function pointer in freed memory, which allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via unspecified vectors.
The product accesses or uses a pointer that has not been initialized.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Kerberos_5 | Mit | 1.4 (including) | 1.4 (including) |
| Kerberos_5 | Mit | 1.4.1 (including) | 1.4.1 (including) |
| Kerberos_5 | Mit | 1.4.2 (including) | 1.4.2 (including) |
| Kerberos_5 | Mit | 1.4.3 (including) | 1.4.3 (including) |
| Kerberos_5 | Mit | 1.4.4 (including) | 1.4.4 (including) |
| Kerberos_5 | Mit | 1.5 (including) | 1.5 (including) |
| Kerberos_5 | Mit | 1.5.1 (including) | 1.5.1 (including) |
| Krb5 | Ubuntu | dapper | * |
| Krb5 | Ubuntu | devel | * |
| Krb5 | Ubuntu | edgy | * |
| Krb5 | Ubuntu | feisty | * |
If the pointer contains an uninitialized value, then the value might not point to a valid memory location. This could cause the product to read from or write to unexpected memory locations, leading to a denial of service. If the uninitialized pointer is used as a function call, then arbitrary functions could be invoked. If an attacker can influence the portion of uninitialized memory that is contained in the pointer, this weakness could be leveraged to execute code or perform other attacks. Depending on memory layout, associated memory management behaviors, and product operation, the attacker might be able to influence the contents of the uninitialized pointer, thus gaining more fine-grained control of the memory location to be accessed.