Code execution via overlong filename during save
Published Oct 24, 2022 · Updated May 7, 2025
Stack-based buffer overflow in WTViewerE 1.31 through 1.61 and WTViewerEfree 1.01 through 1.52 allows attackers to execute code via a long filename. The file-save function mishandles an overlong filename, overflowing a stack buffer in the current process. A user must be induced to enter the long filename; successful exploitation runs code with that process's rights, while failed exploitation crashes the application.
Summary
What happened
Stack-based buffer overflow in WTViewerE 1.31 through 1.61 and WTViewerEfree 1.01 through 1.52 allows attackers to execute code via a long filename. The file-save function mishandles an overlong filename, overflowing a stack buffer in the current process. A user must be induced to enter the long filename; successful exploitation runs code with that process's rights, while failed exploitation crashes the application.
The record
- CVE
- CVE-2022-40984
- Published
- Oct 24, 2022
- Updated
- May 7, 2025
- Vendor
- Yokogawa Test & Measurement Corporation
- Product
- WTViewerE
- Classifications
- CWE-121, CWE-787, T1203
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 24, 2022CVE publishedPublication date reported by the CVE source.
- May 7, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=WTViewerE 761941 from 1.31 to 1.61 and WTViewerEfree from 1.01 to 1.52
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo