dbcve.org
Tofino Xenon Security Appliance FirmwareOperating system · Belden

CVE-2021-30066

MEDIUM · 6.8 CVSS v3.1 Published 2022-04-03
Fix available
A fix is available. Upgrade to 03.2.03 or later.
See remediation →
73/100
Remediation priority · Elevated
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, an arbitrary firmware image can be loaded because firmware signature verification (for a USB stick) can be bypassed. NOTE: this issue exists because of an incomplete fix of CVE-2017-11400.

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 Tofino Firewall and Xenon Security Appliance devices contain a signature verification bypass vulnerability that allows arbitrary firmware to be loaded from a USB stick. This is due to an incomplete fix of the previous CVE-2017-11400, meaning the original signature bypass was not fully remediated. An attacker with physical access to the device can load malicious firmware by inserting a crafted USB device.

MitigationUpdate firmware to version 03.23 or later as specified in the vendor advisory. If immediate patching is not possible, physically secure the devices and disable or restrict USB port access to prevent unauthorized firmware loading.

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

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the exact Tofino device model
    Locate the device label or check the device management interface for the exact model number (e.g., Xenon, Argon TSA 220, Eagle 20 Tofino)
    Affected if The device model matches any of the affected products listed in the CVE (Xenon, Argon variants, Eagle 20 models)
  2. Check the installed firmware version
    Access the device admin interface or CLI and run the command to display firmware version (typically 'show version' or view system information)
    Affected if For Tofino Xenon: firmware version is below 03.2.03. For any Argon or Eagle 20 model: any firmware version (all versions affected)
  3. Verify if USB ports are accessible on the device
    Physically inspect the device USB ports or check device configuration for USB port status/enabled state
    Affected if USB ports are physically present and enabled, allowing firmware loading from USB storage devices
  4. Confirm whether unsigned firmware can be loaded
    Attempt to load firmware from a USB stick or review device documentation/audit logs for firmware update mechanism verification
    Affected if The device accepts firmware loading from USB without proper signature validation, indicating the bypass is present

You are affected if you have a Belden Tofino Xenon device running firmware below version 03.2.03, or any Belden Tofino Argon or Eagle 20 model, and USB ports are accessible for firmware loading.

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 firmware to version 03.23 or later as specified in the vendor advisory. If immediate patching is not possible, physically secure the devices and disable or restrict USB port access to prevent unauthorized firmware loading.

Recommended fix Moderate confidence

Tofino Xenon Security Appliance: Firmware version 03.2.03 or later

  1. 1. Identify the exact model number of your Tofino device (e.g., TCSEFEA23F3F22, Xenon, Argon TSA 220, Eagle 20)
  2. 2. Determine the current firmware version installed on the device
  3. 3. For Tofino Xenon Security Appliance: Navigate to the firmware management section in the device admin interface or consult the device manual
  4. 4. Download the updated firmware version 03.2.03 or later from the official Schneider Electric download portal (download.schneider-electric.com) or Belden (www.belden.com)
  5. 5. Follow the vendor's documented firmware update procedure to apply the new version
  6. 6. Verify the firmware update was successful and the device is operating normally
  7. 7. For devices listed as 'all versions' affected (Argon and Eagle 20 models): Contact Schneider Electric or Belden technical support to confirm if a fix is available for your specific model
Caveat Ensure proper backup of configuration before firmware upgrade; follow vendor's recommended update procedure to avoid devicelockout

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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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