dbcve.org
Tofino Xenon Security Appliance FirmwareOperating system · Belden

CVE-2021-30065

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 Firewall TCSEFEA23F3F22 before 03.23, TCSEFEA23F3F20/21, and Belden Tofino Xenon Security Appliance, crafted ModBus packets can bypass the ModBus enforcer. NOTE: this issue exists because of an incomplete fix of CVE-2017-11401.

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

The ConneXium Tofino Firewall and Belden Tofino Xenon Security Appliance contain a ModBus enforcer bypass vulnerability where crafted ModBus packets can circumvent security controls. This is a regression/incomplete fix from CVE-2017-11401, indicating the original patch did not fully address the underlying weakness in packet validation logic.

MitigationApply vendor firmware updates (version 03.23 or later for affected TCSEFEA23F3F22 models; check Belden for Xenon updates). Verify the ModBus enforcer correctly blocks crafted packets after patching.

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 device model and firmware version
    Access the Tofino device web interface or CLI and navigate to System Information or use the 'show version' command to retrieve the exact firmware version number
    Affected if The firmware version is below 03.2.03 for Xenon models, or matches any of the Argon TSA 100/220 or Eagle 20 model numbers listed (which are all affected)
  2. Confirm ModBus enforcer is configured
    In the Tofino management interface, navigate to the ModBus enforcer settings or check the security policy configuration to verify that ModBus traffic inspection and enforcement rules are active
    Affected if ModBus enforcer is enabled and actively enforcing security policies on ModBus traffic
  3. Verify the ModBus enforcer rule set
    Review the ModBus enforcer rules through the device console or configuration backup to confirm rules are defined for blocking unauthorized ModBus function codes or addresses
    Affected if Rules are defined but may be bypassable due to the vulnerability in packet validation logic
  4. Check for CVE-201-11401 historical context
    Review device documentation or previous vulnerability assessments to determine if this device was previously assessed for CVE-2017-11401 and whether the original patch was applied
    Affected if The device was never patched for CVE-2017-11401 or the patch was incomplete, indicating regression is present

The environment is affected if the device runs a vulnerable firmware version (any Argon/Eagle model, or Xenon firmware below 03.2.03) and has ModBus enforcer configured, since crafted ModBus packets can bypass those security controls.

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

Apply vendor firmware updates (version 03.23 or later for affected TCSEFEA23F3F22 models; check Belden for Xenon updates). Verify the ModBus enforcer correctly blocks crafted packets after patching.

Recommended fix Moderate confidence

Tofino Xenon Security Appliance: firmware 03.2.03 or later; ConneXium Tofino Firewall TCSEFEA23F3F22: firmware 03.23 or later; Other models: contact vendor for patch

  1. 1. Identify the specific Tofino device model and current firmware version
  2. 2. For Tofino Xenon Security Appliance: Download and install firmware version 03.2.03 or later from the Belden download portal (download.schneider-electric.com or Belden support)
  3. 3. For ConneXium Tofino Firewall TCSEFEA23F3F22: Upgrade to firmware version 03.23 or later
  4. 4. For ConneXium Tofino Firewall TCSEFEA23F3F20/21: Contact Schneider Electric for specific patch/firmware update
  5. 5. For Tofino Argon models (TSA 100/220 all variants) and Eagle 20 Tofino models: Contact Schneider Electric/Belden directly for firmware updates, as no fixed version is specified in available documentation
  6. 6. After upgrade, verify the ModBus enforcer is functioning correctly by testing with crafted ModBus packets
  7. 7. Review and validate firewall rules to ensure the ModBus enforcer is properly configured
Caveat Firmware upgrades on industrial security appliances may require downtime and should be tested in a non-production environment first; validate compatibility with existing industrial control system configurations

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
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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