CVE Tools

CVE-2021-37376

Public exploit available. Not confirmed exploited in the wild yet. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

  • Teradek Bond FirmwareAffected: ≥ 7.3.0, ≤ 7.3.18Upgrade to: after 7.3.18Stated by: NVD
  • Teradek Bond 2 FirmwareAffected: ≥ 7.3.0, ≤ 7.3.19Upgrade to: after 7.3.19Stated by: NVD
  • Teradek Bond Pro FirmwareAffected: ≥ 7.3.0, ≤ 7.3.19Upgrade to: after 7.3.19Stated by: NVD

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check whether you run Teradek Bond firmware 7.3.x or earlier and identify who can access its management page.
  2. Limit the management page to trusted staff and private networks; remove unnecessary user accounts and do not expose it directly to the internet.
  3. There is no fixed firmware version: the product is end of life and the vendor will not provide an update, so plan replacement with supported equipment.

What it is

From the CVE record

Cross Site Scripting (XSS) vulnerability in Teradek Bond, Bond 2 and Bond Pro firmware version 7.3.x and earlier allows remote attackers to run arbitrary code via the Friendly Name field in System Information Settings. NOTE: Vedor states the product has reached End of Life and will not be receiving any firmware updates to address this issue.

In plain language

Written by AI from the record

Teradek Bond firmware 7.3.x and earlier has a flaw that can let a logged-in user trick another user’s browser, so affected small businesses should restrict access and plan to replace the device.

Stored XSS in the System Information Friendly Name field allows a low-privileged authenticated attacker to execute script in another user’s browser when the crafted value is viewed.

If you're affected

  • Administrator session theft
  • Device setting changes
  • Live video workflow disruption
  • Unauthorized dashboard actions

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS49th
Public exploit
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

1 source with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

0.6% chance of exploitation activity in the next 30 days, which ranks it in the 49th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

The patch came 471 days before any public exploit.

  1. Public exploit / PoCsource: other
  2. Patch availablerecord updated
  3. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

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

Scored 5.4 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality LowSome restricted information is disclosed, but limited in scope
  • Integrity LowData modification is possible but limited in scope or consequence
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Bond Firmware, not every advisory. This one: public exploit.