auditselect command contains a format string vulnerability that may allow a local attacker to execute arbitrary code.
According to IBM's Command Reference, the syntax and description of the
auditselect command are as follows:
The auditselect command is part of the audit subsystem. The command is called by the auditbin daemon if it is configured in the /etc/security/audit/bincmds file as a backend command for processing bin files.
The auditselect command selects audit records that match identified criteria and writes the records to standard output. With the auditselect command, you can filter the audit trail to obtain specific records for analysis or select specific records for long-term storage. The command takes stream or bin input from the file specified by the Trail parameter or from standard input. If you specify the $bin string as the value of the Trail parameter, the auditbin daemon substitutes the path name of the current bin file when it calls the auditselect command. The selection criteria can be entered as an expression or from the file specified by the -f flag. If the bin files are compressed, the auditselect command unpacks them prior to processing.
There is a format string vulnerability within the
auditselect command due to the way it uses formatted output routines, such as
auditselect command may pass formatted output routines user-supplied data. If a local attacker with audit group membership passes a specially crafted parameter to
auditselect, that parameter may be passed to a formatted output routine. Since output routines in
auditselect do not adequately filter or restrict input (via a format string specifier), the attacker may be able to exploit this vulnerability.
Please note that the
auditselect command executes with
auditselectspecially crafted input, a local attacker with membership in the audit group may be able to execute arbitrary code with
We are currently unaware of a practical solution to this problem.
Restrict Access to Audit Group
To successfully exploit this vulnerability an attacker must have access to the audit group. By restricting membership to the audit group to trusted users, the chances of exploitation are reduced.
Vendor| Status| Date Notified| Date Updated
IBM| | 28 Feb 2005| 28 Feb 2005
If you are a vendor and your product is affected, let us know.
Group | Score | Vector
Base | N/A | N/A
Temporal | N/A | N/A
Environmental | N/A | N/A
This vulnerability was reported by iDEFENSE Security .
This document was written by Jeff Gennari.