dbcve.org
Tofino Xenon Security Appliance FirmwareOperating system · Belden

CVE-2021-30062

HIGH · 7.5 CVSS v3.1 Published 2022-04-03
Fix available
A fix is available. Upgrade to 03.2.03 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
On Schneider Electric ConneXium Tofino OPCLSM TCSEFM0000 before 03.23 and Belden Tofino Xenon Security Appliance, crafted OPC packets can bypass the OPC enforcer.

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 security bypass vulnerability in Schneider Electric ConneXium Tofino OPCLSM and Belden Tofino Xenon Security Appliances allows crafted OPC (Open Platform Communications) packets to circumvent the OPC enforcer firewall module. This enables potentially malicious OPC traffic to pass through the security appliance without inspection, compromising the air-gapped or protected network segments these devices are designed to safeguard.

MitigationUpdate Schneider Electric ConneXium Tofino OPCLSM TCSEFM0000 to firmware version 03.23 or later. For Belden Tofino Xenon, apply vendor-provided patches. Additionally, implement network segmentation and monitor OPC traffic for anomalies as a defensive measure until patching is complete.

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
Tofino Xenon Security Appliance FirmwareOperating system
Affected:< 03.2.03
Tofino Argon Fa Tsa 220 Tx\/mm FirmwareOperating system
Affected:all versions
Tofino Argon Fa Tsa 220 Tx\/tx FirmwareOperating system
Affected:all versions
Tofino Argon Fa Tsa 220 Mm\/tx FirmwareOperating system
Affected:all versions
Tofino Argon Fa Tsa 220 Mm\/mm FirmwareOperating system
Affected:all versions
Tofino Argon Fa Tsa 100 Tx\/tx FirmwareOperating system
Affected:all versions
Eagle 20 Tofino 943 987 505 Mm\/mm FirmwareOperating system
Affected:all versions
Eagle 20 Tofino 943 987 504 Mm\/tx FirmwareOperating system
Affected:all versions

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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 the Tofino device model
    Log into the device web interface or CLI and run 'show system information' or check the device label to confirm the exact model (e.g., Tofino Xenon, Tofino Argon TSA 220, Eagle 20 Tofino)
    Affected if The model is Belden Tofino Xenon, Belden Tofino Argon (any variant), or Belden Eagle 20 Tofino (any variant)
  2. Check the installed firmware version
    In the web interface go to System > Firmware or run 'show version' via CLI. Note the exact firmware version number.
    Affected if For Tofino Xenon: version is lower than 03.2.03. For Argon and Eagle models: any version is affected (all versions)
  3. Confirm the OPC Enforcer module is enabled
    In the Tofino web interface, navigate to Security > OPC Enforcer or run 'show opc enforcer status' via CLI to verify the module is active
    Affected if The OPC Enforcer firewall module is enabled and configured (the bypass only affects environments using this protection)
  4. Verify OPC traffic inspection configuration
    Check the OPC Enforcer ruleset by going to Security > OPC Enforcer > Rules. Confirm there are active rules allowing OPC traffic through the appliance.
    Affected if There are active OPC rules and the appliance is configured to inspect/allow OPC traffic between network segments

You are affected if your device is a Belden Tofino Xenon (firmware < 03.2.03), Belden Tofino Argon (any version), or Belden Eagle 20 Tofino (any version), AND the OPC Enforcer module is enabled and processing OPC traffic.

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.

dbcve · scoped
Upgrade available Upgrade to 03.2.03 or later
Fixed in 03.2.03
Interim mitigation

Update Schneider Electric ConneXium Tofino OPCLSM TCSEFM0000 to firmware version 03.23 or later. For Belden Tofino Xenon, apply vendor-provided patches. Additionally, implement network segmentation and monitor OPC traffic for anomalies as a defensive measure until patching is complete.

Recommended fix High confidence

Tofino Xenon: firmware >= 03.2.03; ConneXium Tofino OPCLSM TCSEFM0000: firmware >= 03.23

  1. 1. Identify the specific Tofino device model and current firmware version from the device management interface
  2. 2. For Tofino Xenon Security Appliance: Navigate to Belden's support portal at www.belden.com or download.schneider-electric.com
  3. 3. For ConneXium Tofino OPCLSM TCSEFM0000: Navigate to Schneider Electric's download portal at download.schneider-electric.com
  4. 4. Locate and download the firmware update: Xenon devices require version 03.2.03 or later; OPCLSM requires version 03.23 or later
  5. 5. Apply firmware update through the device's standard firmware upgrade procedure (typically via web UI or management console)
  6. 6. Verify the firmware version was successfully applied and confirm the OPC enforcer is functioning
Caveat Review release notes for any configuration or compatibility changes between current and new firmware versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tofino Xenon Security Appliance Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

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