Code execution via malformed PLC project data
Published Oct 3, 2024 · Updated Oct 3, 2024
Stack-based buffer overflow in JTEKT KPP 1.6.14.0 and earlier allows attackers to execute code via a crafted project file. Processing invalid PLC data in the KPP project-file parser writes beyond a stack buffer when the file is opened. A user must open a file created by KPP 1.6.9.0 or earlier; exploitation can also disclose information or crash the application.
Summary
What happened
Stack-based buffer overflow in JTEKT KPP 1.6.14.0 and earlier allows attackers to execute code via a crafted project file. Processing invalid PLC data in the KPP project-file parser writes beyond a stack buffer when the file is opened. A user must open a file created by KPP 1.6.9.0 or earlier; exploitation can also disclose information or crash the application.
The record
- CVE
- CVE-2024-47135
- Published
- Oct 3, 2024
- Updated
- Oct 3, 2024
- Vendor
- JTEKT ELECTRONICS CORPORATION
- Product
- KPP (Kostac PLC Programming Software)
- Classifications
- CWE-121, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 3, 2024CVE publishedPublication date reported by the CVE source.
- Oct 3, 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=0 <=1.6.14.0
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