dbcve.org
Tofino Xenon Security Appliance FirmwareOperating system · Belden

CVE-2021-30064

CRITICAL · 9.8 CVSS v3.1 Published 2022-04-03
Fix available
A fix is available. Upgrade to 03.2.03 or later.
See remediation →
100/100
Remediation priority · Urgent
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, an SSH login can succeed with hardcoded default credentials (if the device is in the uncommissioned state).

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

Hardcoded default SSH credentials exist in Schneider Electric ConneXium Tofino Firewall and Belden Tofino Xenon Security Appliance devices. When devices are in the uncommissioned (factory default) state, authentication succeeds with these credentials, allowing unauthenticated remote attackers to gain administrative access.

MitigationEnsure all Tofino devices are properly commissioned before deployment by changing default credentials. For already-deployed devices, verify they are not in uncommissioned state and immediately change any default credentials.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 Tofino device model on the network
    Perform network discovery (e.g., nmap, SNMP sweep) to identify devices with Tofino-specific banners, MAC OUI Belden (00:1D:9C), or SSH banners containing 'Tofino' or 'Belden'. Document the IP address and hostname.
    Affected if The discovered device matches one of the affected product names: Belden Tofino Xenon Security Appliance, Belden Tofino Argon models (TSA 220, TSA 100), or Belden Eagle 20 Tofino models.
  2. Check the installed firmware version
    Access the device web interface, SNMP, or CLI and retrieve the firmware version. For CLI, connect via console or SSH and run 'show version' or equivalent command. Compare the version number against the affected ranges.
    Affected if The device is a Belden Tofino Xenon with firmware version < 03.2.03, OR the device is any Belden Tofino Argon or Eagle 20 model regardless of version.
  3. Determine if the device is in uncommissioned state
    Access the device management interface (web or CLI) and check the commissioning status or initial setup state. Look for indicators such as 'factory default', 'uncommissioned', 'not configured', or an initial setup wizard prompt that indicates default credentials are still active.
    Affected if The device displays as being in factory default, uncommissioned, or not-yet-configured state with default credentials still in place.
  4. Verify SSH access with default credentials
    Attempt an SSH connection to the device using a console or SSH client. Try connecting with the default SSH credentials (root/admin with default password). If authentication succeeds without having changed the password, the device is vulnerable.
    Affected if SSH authentication succeeds with default factory credentials and the device remains in uncommissioned state.

A user is affected if they have a Belden Tofino Xenon (< 03.2.03), Belden Tofino Argon, or Belden Eagle 20 Tofino device that is currently in an uncommissioned (factory default) state with default SSH credentials still active.

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

Ensure all Tofino devices are properly commissioned before deployment by changing default credentials. For already-deployed devices, verify they are not in uncommissioned state and immediately change any default credentials.

Recommended fix Moderate confidence

Tofino Xenon Security Appliance: Firmware 03.2.03 or later; Other models: Contact vendor for model-specific fixed firmware

  1. 1. Identify the specific Tofino device model and current firmware version by accessing the device management interface or checking the device label
  2. 2. For Tofino Xenon Security Appliance: Download firmware version 03.2.03 or later from Schneider Electric's official support portal (download.schneider-electric.com) or Belden's portal (www.belden.com)
  3. 3. For Tofino Argon and Eagle 20 models: Check Schneider Electric or Belden product security advisories for the latest fixed firmware releases applicable to your specific model number
  4. 4. Follow the vendor's published firmware upgrade procedure, which typically involves: uploading the firmware file through the device's web interface or CLI, verifying the image integrity, and initiating the upgrade
  5. 5. After upgrading, ensure the device is properly commissioned (taken out of uncommissioned state) per vendor guidance to disable the default credentials
  6. 6. Verify the upgrade was successful by confirming the new firmware version and testing that default credentials no longer provide access
Caveat Review vendor release notes for any configuration or compatibility changes before upgrading production devices

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
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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