dbcve.org
Kostac PlcApplication · Jtekt

CVE-2024-47136

HIGH · 7.8 CVSS v3.1 Published 2024-10-03
Fix available
A fix is available. Upgrade to 1.6.15.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 read 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 · moderate confidence

An out-of-bounds read vulnerability exists in Kostac PLC Programming Software versions 1.6.14.0 and earlier when parsing specially crafted KPP project files. The vulnerability is triggered when a user opens a malicious project file that was saved using version 1.6.9.0 or earlier, leading to potential denial-of-service, arbitrary code execution, or information disclosure.

MitigationUpdate Kostac PLC Programming Software to a version beyond 1.6.14.0 when a patch is available. Until then, avoid opening KPP project files from untrusted sources or verify files originate from trusted, unmodified versions.

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 PlcApplication
Affected:< 1.6.15.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. Check if Kostac PLC Programming Software is installed
    Look for the application in the system program list, or search for executable files named 'Kostac' or related PLC programming tools in Program Files directories
    Affected if The software is not found on the system
  2. Determine the installed version of Kostac PLC Programming Software
    Open the application and navigate to Help > About, or right-click the executable and select Properties > Details to view the version number
    Affected if Unable to determine the version number
  3. Compare installed version against the affected range
    Review the version number found in the previous step and compare it to the vulnerable range: versions 1.6.14.0 and earlier (anything below 1.6.15.0)
    Affected if The installed version is 1.6.14.0 or earlier, or any version below 1.6.15.0
  4. Verify KPP file handling capability
    Attempt to open or create a KPP project file within the installed software, or check file association settings for .kpp files
    Affected if The software can open KPP files and no separate module needs to be enabled - this is a core function of the software

The environment is affected if Kostac PLC Programming Software is installed with any version below 1.6.15.0 and the software can handle KPP project files, as the vulnerability is triggered when parsing specially crafted KPP 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.15.0 or later
Fixed in 1.6.15.0
Interim mitigation

Update Kostac PLC Programming Software to a version beyond 1.6.14.0 when a patch is available. Until then, avoid opening KPP project files from untrusted sources or verify files originate from trusted, unmodified versions.

Recommended fix High confidence

1.6.15.0

  1. Check current installed version of Kostac PLC Programming Software by opening the application and navigating to Help > About or checking the program properties
  2. Back up all existing project files (KPP files) before upgrading to prevent data loss
  3. Download Kostac PLC Programming Software version 1.6.15.0 from the official vendor website (www.electronics.jtekt.co.jp) or your organization's software distribution channel
  4. Run the installer for version 1.6.15.0 with administrator privileges
  5. Follow the on-screen installation wizard prompts to complete the upgrade
  6. After installation, verify the version by checking Help > About to confirm version 1.6.15.0 is installed
  7. Open existing project files to verify they load correctly after the upgrade

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

Fix this in Kostac Plc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,100
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47136 — 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-47136 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