Skip to main content
Mallory
LowVulnerability

CVE-2023-28355: Improper PLC Application Integrity Check in CODESYS Control Runtime

Updated 4 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS0.0Low
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2023-28355CWE-354

CVE-2023-28355 is an improper validation of integrity check value vulnerability in the CODESYS Control Runtime used in Schneider Electric devices that embed the CODESYS Runtime System V3. The PLC application code executed by the runtime relies on a checksum mechanism that is not sufficient to reliably detect PLC application code modified in memory or boot application files that have been manipulated. As a result, the integrity verification mechanism can be bypassed by altered application content, allowing unauthorized modifications to persist without dependable detection by the runtime.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can compromise the integrity of PLC application code and boot application files on affected devices. An attacker with the necessary access could alter control logic or runtime-resident application content without reliable detection by the checksum mechanism, enabling unauthorized changes to industrial process behavior. The documented impact is integrity loss rather than confidentiality or availability loss, reflected by CVSS v3.1 6.5 with high integrity impact.

Mitigation

If you can’t patch tonight, do this now.

Restrict access to device programming and engineering interfaces, enable user management with strong authentication, and use encrypted communication links where supported. Limit exposure of programming ports to trusted administrative networks only, segment control networks behind firewalls, and use secure remote access methods such as VPNs. Minimize direct network reachability of affected controllers and HMIs from untrusted networks to reduce the likelihood of authenticated tampering.

Remediation

Patch, then assume compromise.

Apply Schneider Electric firmware and software updates for affected products that incorporate the vendor-provided fixes for the underlying CODESYS runtime issue. Reported fixed versions include updates delivered through EcoStruxure Machine Expert v2.2 for certain Modicon and PacDrive product lines, Vijeo Designer 6.3.1 or later for affected HMISCU-related components, and other product-specific updates identified by Schneider Electric. For legacy end-of-life products where no fix is planned, migration to supported replacement platforms is recommended.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2023-28355 exploited in the wild?
As of Jul 31, 2026, Mallory has no reports of CVE-2023-28355 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2023-28355?
As of Jul 31, 2026, Mallory has found no public exploit for CVE-2023-28355.
Is there a patch for CVE-2023-28355?
Apply Schneider Electric firmware and software updates for affected products that incorporate the vendor-provided fixes for the underlying CODESYS runtime issue. Reported fixed versions include updates delivered through EcoStruxure Machine Expert v2.2 for certain Modicon and PacDrive product lines, Vijeo Designer 6.3.1 or later for affected HMISCU-related components, and other product-specific updates identified by Schneider Electric.
How severe is CVE-2023-28355?
CVE-2023-28355 has a CVSS score of 0.0 (Low) as of Jul 31, 2026.
Activity feed

Recent activity

4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.