Memory corruption via tampered log file
Published Aug 9, 2023 · Updated Oct 9, 2024
Memory corruption in Schneider Electric WinGP 4.09.450 and earlier allows attackers to corrupt memory via a tampered GP-Pro EX log file. The vendor identifies log-file handling as the trigger but does not disclose the parser, malformed field, or exact out-of-bounds operation. A logged-in user must open the attacker-supplied file; the documented consequence is memory corruption with low confidentiality, integrity, and availability impact.
Summary
What happened
Memory corruption in Schneider Electric WinGP 4.09.450 and earlier allows attackers to corrupt memory via a tampered GP-Pro EX log file. The vendor identifies log-file handling as the trigger but does not disclose the parser, malformed field, or exact out-of-bounds operation. A logged-in user must open the attacker-supplied file; the documented consequence is memory corruption with low confidentiality, integrity, and availability impact.
The record
- CVE
- CVE-2023-3953
- Published
- Aug 9, 2023
- Updated
- Oct 9, 2024
- Vendor
- Distributed Data Systems
- Product
- WinGP for IPC
- Classifications
- CWE-119, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 9, 2023CVE publishedPublication date reported by the CVE source.
- Oct 9, 2024Record 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=v4.09.450 and prior
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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