Format string vulnerability in Asterisk Open Source 1.6.x before 1.6.0-beta6 might allow remote attackers to execute arbitrary code via logging messages that are not properly handled by (1) the ast_verbose logging API call, or (2) the astman_append function.
The product uses a function that accepts a format string as an argument, but the format string originates from an external source.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Open_source | Asterisk | 1.6.0_beta1 (including) | 1.6.0_beta1 (including) |
| Open_source | Asterisk | 1.6.0_beta2 (including) | 1.6.0_beta2 (including) |
| Open_source | Asterisk | 1.6.0_beta3 (including) | 1.6.0_beta3 (including) |
| Open_source | Asterisk | 1.6.0_beta4 (including) | 1.6.0_beta4 (including) |
| Open_source | Asterisk | 1.6.0_beta5 (including) | 1.6.0_beta5 (including) |
| Asterisk | Ubuntu | dapper | * |
| Asterisk | Ubuntu | devel | * |
| Asterisk | Ubuntu | edgy | * |
| Asterisk | Ubuntu | feisty | * |
| Asterisk | Ubuntu | gutsy | * |
| Asterisk | Ubuntu | hardy | * |
| Asterisk | Ubuntu | intrepid | * |
| Asterisk | Ubuntu | jaunty | * |
| Asterisk | Ubuntu | karmic | * |
When an attacker can modify an externally-controlled format string, this can lead to buffer overflows, denial of service, or data representation problems. It should be noted that in some circumstances, such as internationalization, the set of format strings is externally controlled by design. If the source of these format strings is trusted (e.g. only contained in library files that are only modifiable by the system administrator), then the external control might not itself pose a vulnerability.