CVE-2021-30063
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 · uneditedOn Schneider Electric ConneXium Tofino OPCLSM TCSEFM0000 before 03.23 and Belden Tofino Xenon Security Appliance, crafted OPC packets can cause an OPC enforcer denial of service.
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 confidenceThe vulnerability affects Schneider Electric ConneXium Tofino OPCLSM (TCSEFM0000) before version 03.23 and Belden Tofino Xenon Security Appliance. Attackers can send specially crafted OPC (Open Platform Communications) packets to trigger a denial of service condition in the OPC enforcer component, disrupting industrial process communications.
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< 03.2.03all versionsall versionsall versionsall versionsall versionsall 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Tofino device modelAccess the device management interface or check physical device labeling to determine if it is a Xenon Security Appliance, Argon Fa Tsa (100/220), or Eagle 20 Tofino model.Affected if The device is any of the Belden Tofino models listed in the affected products.
-
Check firmware version on Tofino XenonLog into the Xenon management console and navigate to System > Firmware or use the 'show version' command. For Xenon, compare the version number against 03.2.03.Affected if The firmware version is below 03.2.03 on a Tofino Xenon Security Appliance.
-
Check if device is an affected Argon or Eagle modelVerify if the device is one of the Argon Fa Tsa 220 (any variant), Argon Fa Tsa 100 Tx/tx, or Eagle 20 Tofino 943 987 505/504 models. These have no version threshold and are all affected.Affected if The device is any Argon Fa Tsa 220, Argon Fa Tsa 100 Tx/tx, or Eagle 20 Tofino model regardless of version.
-
Verify OPC enforcer is activeCheck the device configuration for OPC Enforcer module status. In the Tofino management interface, navigate to Security Policies or OPC Enforcer settings to see if it is enabled.Affected if The OPC Enforcer component is enabled and the device is in the affected product list.
You are affected if you run any Belden Tofino Xenon below firmware 03.2.03, or any Argon Fa Tsa or Eagle 20 Tofino model with OPC Enforcer enabled.
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 data03.2.03
Upgrade the ConneXium Tofino OPCLSM to firmware version 03.23 or later. For Belden Tofino Xenon, apply the corresponding vendor patch. Additionally, network segmentation and OPC traffic filtering can provide defense-in-depth while patching is scheduled.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30063 — 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-2021-30063 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