Vulnerability Note VU#813631
Total Commander File Info plugin vulnerable to denial of service via an out-of-bounds read
Original Release date: 20 Jul 2015 | Last revised: 20 Jul 2015
Total Commander’s File Info plugin version 2.21 attempts an out-of-bounds read when reading a file carefully crafted by an attacker.
CWE-125: Out-of-bounds Read – CVE-2015-2869
An attacker that can control the contents of certain file types may be able to cause an out-of-bounds read error in Total Commander File Plugin version 2.21 by specifying overly large values of certain properties. An attacker who successfully exploits this vulnerability may cause the Total Commander application to unexpectedly terminate.
This attack has been noted in at least two different file types due to the software’s improper use of the strncmp function.
COFF Archive Library (.lib) files may be used by specifying overly large values for the ‘Size’ field of the Archive Member Header or the "Number Of Symbols" field in the 1st Linker Member.
Linear Executable files may be used by specifying overly large values for the "Resource Table Count" field of the LE Header or the "Object" field at offset 0x8 from a "Resource Table Entry".
Out-of-bounds reads may allow remote code execution in some circumstances; the CERT/CC is currently unaware of such an attack on the Total Commander File Info plugin, however.
An attacker may be able to cause the application to terminate.
Apply an update
Total Commander File Info plugin has released version 2.22, which addresses this issue. Affected users are encouraged to update as soon as possible
Vendor Information (Learn More)
VendorStatusDate NotifiedDate UpdatedTotal Commander File Info PluginAffected-16 Jul 2015If you are a vendor and your product is affected, let
CVSS Metrics (Learn More)
Thanks to Cisco TALOS for reporting this vulnerability to us. Cisco Talos credits Marcin Noga for discovering this vulnerability.
This document was written by Garret Wassermann.
16 Jul 2015
Date First Published:
20 Jul 2015
Date Last Updated:
20 Jul 2015
FeedbackIf you have feedback, comments, or additional information about this vulnerability, please send us email.