CVE-2015-2869
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe FileInfo plugin before 2.22 for Ghisler Total Commander allows remote attackers to cause a denial of service (out-of-bounds read and application crash) via (1) a large Size value in the Archive Member Header of a COFF Archive Library file, (2) a large Number Of Symbols value in the 1st Linker Member of a COFF Archive Library file, (3) a large Resource Table Count value in the LE Header of a Linear Executable file, or (4) a large value in a certain Object field in a Resource Table Entry in a Linear Executable file.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe FileInfo plugin before version 2.22 in Total Commander contains multiple out-of-bounds read vulnerabilities when parsing malformed COFF Archive Library and Linear Executable files. Specifically, the plugin fails to properly validate Size values, Number Of Symbols counts, and Resource Table counts in these file formats, leading to memory access violations and application crashes when processing specially crafted files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.2.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the FileInfo plugin installationOpen Total Commander and navigate to menu: Configuration > Options > Plugins. Find FileInfo in the list of installed plugins, or check the plugin directory (typically \TOTALCMD\Plugins\fileinfo\ or %APPDATA%\Ghisler\TotalCommander\Plugins\fileinfo\).Affected if The FileInfo plugin is not installed, then the vulnerability does not apply.
-
Determine the FileInfo plugin versionIn the Plugins configuration window, select FileInfo and click Details or Properties to view the version number. Alternatively, check the plugin DLL file properties (usually wlx_fileinfo.dll or similar) for the version metadata.Affected if The displayed version is 2.2.1 or lower.
-
Confirm the plugin is enabled for file operationsIn Total Commander, verify that FileInfo is assigned as a Lister plugin (WLX) and is active. Go to Configuration > Options > Plugins > Lister plugin (WLX) and ensure FileInfo is listed and checked/enabled.Affected if The plugin is disabled or not assigned, the vulnerability cannot be triggered through Total Commander file preview.
-
Check for recent use of COFF or Linear Executable filesReview any recently opened files in Total Commander's history, or check the Lister plugin's file associations. COFF Archive Library files typically have .lib or .coff extensions; Linear Executable files use .exe, .dll, or .sys extensions in certain contexts.Affected if Untrusted COFF or Linear Executable files have been opened using Total Commander's Lister with FileInfo.
You are affected if the FileInfo plugin version is 2.2.1 or lower, the plugin is enabled, and you have opened or previewed untrusted COFF Archive Library or Linear Executable files using Total Commander.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade FileInfo plugin to version 2.22 or later to patch the out-of-bounds read vulnerabilities. Avoid opening untrusted COFF Archive Library and Linear Executable files with Total Commander until the patch is applied.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2869 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-2869 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data