dbcve.org
Kostac Plc Programming SoftwareApplication · Jtekt

CVE-2023-22424

HIGH · 7.8 CVSS v3.1 Published 2023-03-06
Fix available
A fix is available. Upgrade to after 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
Use-after-free vulnerability exists in Kostac PLC Programming Software (Former name: Koyo PLC Programming Software) Version 1.6.9.0 and earlier. With the abnormal value given as the maximum number of columns for the PLC program, the process accesses the freed memory. As a result, opening a specially crafted project file may lead to information disclosure and/or arbitrary code execution.

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 use-after-free vulnerability in Kostac PLC Programming Software versions 1.6.9.0 and earlier allows memory corruption when processing specially crafted project files containing abnormal values for the maximum number of PLC program columns. This causes the application to access freed memory, potentially leading to information disclosure and/or arbitrary code execution.

MitigationUpgrade to a version newer than 1.6.9.0, avoid opening untrusted project files, and apply network segmentation for industrial control system environments.

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

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. Identify installed Kostac PLC Programming Software version
    Open the software and navigate to Help > About, or check the installed program's version property in Windows Add/Remove Programs. The version is typically displayed in the format X.X.X.X
    Affected if Version displayed is 1.6.9.0 or earlier (e.g., 1.6.8.0, 1.6.0.0)
  2. Locate the software executable for version confirmation
    Navigate to the installation directory (commonly C:\Program Files\Kostac\PLC Programming Software or C:\Program Files (x86)\Kostac\PLC Programming Software) and right-click the main .exe file to view Properties > Details for the File Version
    Affected if File version shows 1.6.9.0 or lower
  3. Check for project file handling exposure
    Identify whether the software is configured to automatically open or can be directed to open project files from untrusted sources, including network shares, email attachments, or external removable media
    Affected if Users routinely open .kpp or other project files from untrusted or external sources without prior validation
  4. Review recent project file access
    Examine the application's recent files list (File > Recent) or check the application logs if available, for any project files with unusual or abnormally large column count parameters
    Affected if Any project files processed by the software originated from untrusted sources
  5. Verify user privileges when processing project files
    Confirm whether the software runs with elevated privileges or as an administrator when opening project files, which would increase the potential impact of arbitrary code execution
    Affected if Software runs with administrator or elevated privileges and processes project files

A user is affected if the installed Kostac PLC Programming Software version is 1.6.9.0 or earlier AND the software is used to open project files, particularly from untrusted sources.

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.

From vendor data
Upgrade available Upgrade to a release after 1.6.9.0
Interim mitigation

Upgrade to a version newer than 1.6.9.0, avoid opening untrusted project files, and apply network segmentation for industrial control system environments.

Fix this in Kostac Plc Programming Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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