dbcve.org
PlcwinntApplication · Codesys

CVE-2019-19789

MEDIUM · 6.5 CVSS v3.1 Published 2019-12-20
Fix available
A fix is available. Upgrade to 2.3.7.28 / 2.4.7.54 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
3S-Smart CODESYS SP Realtime NT before V2.3.7.28, CODESYS Runtime Toolkit 32 bit full before V2.4.7.54, and CODESYS PLCWinNT before V2.4.7.54 allow a NULL pointer dereference.

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

A NULL pointer dereference vulnerability exists in multiple 3S-Smart CODESYS runtime components (CODESYS SP Realtime NT, CODESYS Runtime Toolkit 32 bit full, and CODESYS PLCWinNT) in versions prior to the specified patches. This memory corruption issue can lead to a denial-of-service condition when triggered.

MitigationUpdate CODESYS SP Realtime NT to V2.3.7.28 or later, and update CODESYS Runtime Toolkit 32 bit full and PLCWinNT to V2.4.7.54 or later. In the interim, restrict network access to vulnerable components and monitor for service disruptions.

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
PlcwinntApplication
Affected:< 2.4.7.54
Runtime ToolkitApplication
Affected:< 2.4.7.54
Sp Realtime NtApplication
Affected:< 2.3.7.28

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 CODESYS components
    Check for CODESYS runtime installations. Look in standard installation directories such as 'C:\Program Files\3S Software\' or 'C:\Program Files (x86)\3S Software\' for folders named PLCWinNT, CODESYS Runtime Toolkit, or CODESYS SP Realtime NT. Also check Windows Services for 'CODESYS' or 'PLCWinNT' services.
    Affected if Any of the three affected components (Plcwinnt, Runtime Toolkit, or Sp Realtime Nt) are present on the system.
  2. Determine PLCWinNT version
    If PLCWinNT is installed, locate its main executable (typically named PLCWinNT.exe or similar). Right-click the file, select Properties, and check the Version tab for the Product Version. Alternatively, run 'wmic product where "name like '%CODESYS%'" get name,version' to list installed CODESYS products.
    Affected if The version is lower than 2.4.7.54.
  3. Determine CODESYS Runtime Toolkit version
    If the CODESYS Runtime Toolkit is installed, locate its executable files (commonly in a subfolder under the 3S Software directory). Right-click the main executable, select Properties, and check the Version tab for the Product Version.
    Affected if The version is lower than 2.4.7.54.
  4. Determine CODESYS SP Realtime NT version
    If CODESYS SP Realtime NT is installed, locate its main executable (typically named CmpSPSRealtime or similar). Right-click the file, select Properties, and check the Version tab for the Product Version.
    Affected if The version is lower than 2.3.7.28.
  5. Verify if vulnerable components are running
    Open Task Manager or run 'tasklist /FI "IMAGENAME eq PLCWinNT.exe"' to check if PLCWinNT is running. For CODESYS Runtime Toolkit or SP Realtime NT, look for related processes in Task Manager or run 'net start | findstr -i codesys' to check running CODESYS services.
    Affected if Any affected component version is currently running.

If any of the three CODESYS components (Plcwinnt, Runtime Toolkit, or SP Realtime Nt) are installed with a version below 2.4.7.54 (for the first two) or 2.3.7.28 (for the third), the system is vulnerable to the NULL pointer dereference denial-of-service flaw.

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 2.3.7.28 / 2.4.7.54 or later
Fixed in 2.3.7.282.4.7.54
Interim mitigation

Update CODESYS SP Realtime NT to V2.3.7.28 or later, and update CODESYS Runtime Toolkit 32 bit full and PLCWinNT to V2.4.7.54 or later. In the interim, restrict network access to vulnerable components and monitor for service disruptions.

Fix this in Plcwinnt Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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