dbcve.org
Kostac Plc Programming SoftwareApplication · Electronics.jtekt

CVE-2024-47134

HIGH · 7.8 CVSS v3.1 Published 2024-10-03
Fix available
A fix is available. Upgrade to 1.6.9.0 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Out-of-bounds write vulnerability exists in Kostac PLC Programming Software (Former name: Koyo PLC Programming Software) Version 1.6.14.0 and earlier. Having a user open a specially crafted project file which was saved using Kostac PLC Programming Software Version 1.6.9.0 and earlier may cause a denial-of-service (DoS) condition, arbitrary code execution, and/or information disclosure because the issues exist in parsing of KPP project files.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Out-of-bounds write vulnerability in Kostac PLC Programming Software versions 1.6.14.0 and earlier when parsing specially crafted KPP project files (those saved using version 1.6.9.0 or earlier). The vulnerability allows denial-of-service, arbitrary code execution, or information disclosure due to improper bounds checking during file parsing.

MitigationUpdate Kostac PLC Programming Software to a version newer than 1.6.14.0. Avoid opening untrusted or specially crafted KPP project files until the software is updated.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Kostac Plc Programming SoftwareApplication
Affected:< 1.6.9.0>= 1.6.10.0, <= 1.6.14.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Kostac PLC Programming Software installation
    Check common installation directories such as C:\Program Files\Kostac PLC Programming Software or C:\Program Files (x86)\Kostac PLC Programming Software, and look for executables named KPP.exe, KPPStudio.exe, or similar Kostac-related executables.
    Affected if The software is found installed on the system.
  2. Determine installed software version
    Right-click the main executable (such as KPP.exe or KPPStudio.exe) in the installation folder, select Properties, and check the Details tab for the File Version or Product Version field.
    Affected if The version cannot be determined or is lower than 1.6.15.0.
  3. Compare version against affected ranges
    If the version is identified, compare it to the affected ranges: versions < 1.6.9.0 OR versions 1.6.10.0 through 1.6.14.0 are vulnerable.
    Affected if The installed version is < 1.6.9.0 OR is between 1.6.10.0 and 1.6.14.0 inclusive.
  4. Identify KPP project file handling
    Check if the software is configured to handle or parse .KPP project files. Look for recent .KPP files in the system or check file association settings for .KPP extension.
    Affected if The software parses .KPP files and the system contains such files, particularly those saved using version 1.6.9.0 or earlier.

A system is affected if Kostac PLC Programming Software is installed with a version lower than 1.6.9.0 or between 1.6.10.0 and 1.6.14.0 inclusive, and the software parses .KPP project files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.6.9.0 or later
Fixed in 1.6.9.0
Interim mitigation

Update Kostac PLC Programming Software to a version newer than 1.6.14.0. Avoid opening untrusted or specially crafted KPP project files until the software is updated.

Recommended fix Moderate confidence

Contact vendor for latest version > 1.6.14.0 (based on affected version range, 1.6.9.0 may be a partial fix; the vendor should confirm the definitive fixed release)

  1. 1. Identify the current installed version of Kostac PLC Programming Software by opening the application and checking 'Help' > 'About' or the software properties
  2. 2. If the installed version is < 1.6.9.0 or >= 1.6.10.0 and <= 1.6.14.0, the software is vulnerable
  3. 3. Contact Koyo Electronics (JTEKT) directly or visit the official vendor website at www.electronics.jtekt.co.jp to obtain the fixed version
  4. 4. Before upgrading, back up all existing project files (.kpp files) to a secure location
  5. 5. Uninstall the current vulnerable version of Kostac PLC Programming Software
  6. 6. Install the latest fixed version from the official vendor source
  7. 7. After installation, verify the version number matches the fixed release (ensure it is > 1.6.14.0 or the specific version the vendor designates as fixed)
  8. 8. Test that project files open correctly in the new version
Caveat Review release notes from Koyo Electronics (JTEKT) for any changes to project file compatibility or functionality

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kostac Plc Programming Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47134 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-47134 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data