Memory corruption via malformed PRJ file parsing
Published Jun 17, 2025 · Updated Jun 17, 2025
Heap-based buffer overflow in LS ELECTRIC GMWIN 4.18 allows attackers to corrupt memory by inducing a user to open a crafted PRJ file. The PRJ parser fails to validate user-supplied data before accessing heap-allocated structures, producing reads and writes past their boundaries. Active user interaction is required, and the resulting out-of-bounds accesses disclose or alter application memory.
Summary
What happened
Heap-based buffer overflow in LS ELECTRIC GMWIN 4.18 allows attackers to corrupt memory by inducing a user to open a crafted PRJ file. The PRJ parser fails to validate user-supplied data before accessing heap-allocated structures, producing reads and writes past their boundaries. Active user interaction is required, and the resulting out-of-bounds accesses disclose or alter application memory.
The record
- CVE
- CVE-2025-49850
- Published
- Jun 17, 2025
- Updated
- Jun 17, 2025
- Vendor
- LS ELECTRIC
- Product
- GMWIN
- Classifications
- CWE-122, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 17, 2025CVE publishedPublication date reported by the CVE source.
- Jun 17, 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=Version 4.18
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