CVE-2019-13533
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 · uneditedIn Omron PLC CJ series, all versions, and Omron PLC CS series, all versions, an attacker could monitor traffic between the PLC and the controller and replay requests that could result in the opening and closing of industrial valves.
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 confidenceThis is a replay attack vulnerability in Omron PLC CJ and CS series where the communication between the PLC and controller lacks proper session validation (e.g., timestamps, sequence numbers, or cryptographic nonces). An attacker with network access can monitor traffic and replay valid commands to open or close industrial valves, achieving unauthorized physical control of industrial processes.
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 dataall versionsall versionsCVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Omron CJ/CS PLCs on the networkReview network inventory or scan for devices with Omron CJ-series or CS-series identifiers. Use PLC programming software (e.g., CX-Programmer) or network scanning tools to confirm the model family.Affected if Omron CJ-series or CS-series PLCs are present on the network
-
Assess network accessibility of the PLCDetermine if the PLC is directly accessible from network segments outside the trusted control network. Check firewall rules, VLAN assignments, and physical network connectivity to identify if untrusted actors can reach the PLC.Affected if The PLC is reachable from untrusted network segments or has no network isolation
-
Verify session validation on PLC communicationsInspect the communication configuration between the PLC and its controller. Check if the protocol (e.g., FINS, Ethernet/IP) implements timestamps, sequence numbers, or cryptographic nonces. Review PLC and controller settings for session token or validity window configurations.Affected if No session validation mechanisms (timestamps, sequence numbers, or nonces) are configured or enforced in the PLC-controller communication
-
Confirm network segmentation existsReview network architecture documents and firewall policies to verify that the PLC resides in an isolated control network segment separated from enterprise IT and external networks.Affected if The PLC shares a network segment with untrusted systems or lacks logical/physical isolation
-
Check for transport encryptionExamine whether communications between the PLC and controller are encrypted (e.g., TLS, IPsec). Verify that protocol settings enable encryption or that a VPN protects the control network traffic.Affected if PLC communications are transmitted in plaintext without encryption or VPN protection
You are affected if Omron CJ or CS series PLCs are network-accessible without proper session validation, segmentation, or encryption, allowing an attacker to capture and replay valid commands.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement replay attack mitigations such as session tokens, sequence numbers, or timestamps with validity windows on PLC communications. Additionally, network segmentation and encryption (e.g., TLS) between the PLC and controller can prevent unauthorized traffic monitoring and replay.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13533 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-13533 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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