CVE-2023-54334
Buffer Overflow in Explorer32++ SEH Allows Code Execution
Publication date: 2026-01-13
Last updated on: 2026-01-13
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| unknown_vendor | explorer32++ | 1.3.5.531 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-121 | A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2023-54334 is a buffer overflow vulnerability in Explorer32++ version 1.3.5.531. It occurs due to improper handling of Structured Exception Handler (SEH) records when a file name argument longer than 396 characters is provided. This causes corruption of the SEH chain, which attackers can exploit to execute arbitrary code on the affected system. [1, 3]
How can this vulnerability impact me? :
This vulnerability can allow an attacker with local access and low privileges to execute arbitrary code on your system by supplying a specially crafted long file name. This can lead to full compromise of confidentiality, integrity, and availability of the affected system, potentially allowing malicious code execution and control over the system. [1, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of Explorer32++ version 1.3.5.531 on your system and monitoring for unusually long file name arguments exceeding 396 characters being passed to Explorer32++.exe. Detection commands could include scanning for the executable version and searching for file operations involving long file names. For example, on Windows, you might use PowerShell commands to check the file version: Get-Item 'C:\Path\To\Explorer32++.exe' | Select-Object VersionInfo. Additionally, monitoring logs or using process monitoring tools to detect execution of Explorer32++.exe with long file name arguments could help identify exploitation attempts. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include avoiding the use of Explorer32++ version 1.3.5.531, especially avoiding opening or processing files with names longer than 396 characters. If possible, upgrade to a newer, patched version of Explorer++ or switch to an alternative file manager. Restrict local user privileges to limit exploitation potential and educate users to avoid interacting with suspicious files or inputs that could trigger the vulnerability. [1, 3]