dbcve.org
Kostac PlcApplication · Jtekt

CVE-2023-41374

HIGH · 7.8 CVSS v3.1 Published 2023-09-20
Fix available
A fix is available. Upgrade to 1.6.10.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
Double free issue exists in Kostac PLC Programming Software Version 1.6.11.0 and earlier. Arbitrary code may be executed by having a user open a specially crafted project file which was saved using Kostac PLC Programming Software Version 1.6.9.0 and earlier because the issue exists in parsing of KPP project files. The vendor states that Kostac PLC Programming Software Version 1.6.10.0 or later implements the function which prevents a project file alteration. Therefore, to mitigate the impact of these vulnerabilities, a project file which was saved using Kostac PLC Programming Software Version 1.6.9.0 and earlier needs to be saved again using Kostac PLC Programming Software Version 1.6.10.0 or later.

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

A double-free vulnerability exists in Kostac PLC Programming Software versions 1.6.11.0 and earlier when parsing KPP project files. Opening a specially crafted project file (originally saved using v1.6.9.0 or earlier) triggers a double-free condition during parsing, potentially allowing arbitrary code execution with the privileges of the user who opened the file.

MitigationUpdate to Kostac PLC Programming Software version 1.6.10.0 or later and re-save all project files that were originally created with version 1.6.9.0 or earlier using the newer version to apply the file alteration prevention feature.

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.10.0= 1.6.11.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 installed Kostac PLC Programming Software version
    Open the software and navigate to Help > About, or check the program's file properties (right-click the executable > Properties > Details). Look for the version number displayed.
    Affected if The version is less than 1.6.10.0 or equals 1.6.11.0
  2. Identify KPP project files in use
    Search the system for .kpp files. Check project directories, recent files, or the software's default project save location for KPP files.
    Affected if KPP project files exist on the system that were originally saved using version 1.6.9.0 or earlier
  3. Verify if project files retain old version metadata
    Open the KPP files in a hex editor or text editor and look for version strings. In the software, check the project properties or file info for the original creation version.
    Affected if Any KPP file shows it was originally created with version 1.6.9.0 or earlier and has not been re-saved with version 1.6.10.0 or later
  4. Confirm KPP file parsing is active
    Attempt to open any KPP project file in the software, or monitor the process when receiving/opening KPP files from external sources.
    Affected if The software parses KPP files without additional security sandboxing or validation

You are affected if you have Kostac PLC Programming Software versions 1.6.11.0 or earlier AND open KPP project files that were originally saved with version 1.6.9.0 or earlier.

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.10.0 or later
Fixed in 1.6.10.0
Interim mitigation

Update to Kostac PLC Programming Software version 1.6.10.0 or later and re-save all project files that were originally created with version 1.6.9.0 or earlier using the newer version to apply the file alteration prevention feature.

Recommended fix High confidence

Kostac PLC Programming Software Version 1.6.12.0 or latest available

  1. Identify the current installed version of Kostac PLC Programming Software by checking the application properties or 'About' section
  2. Download Kostac PLC Programming Software Version 1.6.12.0 (or the latest available version) from the official vendor website at www.electronics.jtekt.co.jp
  3. Install the new version following the vendor's standard installation procedure
  4. After upgrading, open any existing project files that were originally saved using Version 1.6.9.0 or earlier
  5. Re-save all project files using Version 1.6.10.0 or later to activate the project file alteration prevention function
  6. Verify that the re-saved project files open correctly in the new version
Caveat Review release notes for any changes in project file format compatibility or functionality before upgrading production systems

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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