Tripwire contains a flaw that may allow a malicious user to execute arbitrary code. The issue is triggered when creating a file with a specially crafted filename which may be included in the email report and passed to the fprintf() function. It is possible that the flaw may allow arbitrary code execution resulting in a loss of integrity.
Classification
Location:
Local Access Required
Attack Type:
Input Manipulation
Impact:
Loss of Integrity
Exploit:
Exploit Unknown
Disclosure:
OSVDB Verified
Technical
The format string issue is only present in the code that processes email reports when the MAILMETHOD is used via sendmail. As such, this vulnerability does not affect Windows versions of Tripwire, nor *nix versions that are configured to use another email processor such as SMTP.
Solution
Currently, there are no known workarounds or upgrades to correct this issue. However, Paul Herman has released a patch to address this vulnerability.
This product uses the Daylife API but is not endorsed or certified by Daylife.
This section lists the latest news and blogs found via the daylife API (and for older items, the technorati API), which mention or otherwise discuss this vulnerability.