LiveActive security incident?Get immediate response
CVE Record

CVE-2021-21962: A heap-based buffer overflow vulnerability exists in the OTA Update u-download functionality of Sealevel Sy...

A heap-based buffer overflow vulnerability exists in the OTA Update u-download functionality of Sealevel Systems, Inc. SeaConnect 370W v1.3.34. A series of specially-crafted MQTT payloads can lead to remote code execution. An attacker must perform a man-in-the-middle attack in order to trigger this vulnerability.

CriticalCVSS 9Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2021-21962 is a critical flaw in Sealevel Systems SeaConnect 370W firmware v1.3.34. A network attacker who can place themselves in the device’s traffic path could abuse OTA update handling and potentially run code on the device. The source bundle does not show confirmed active exploitation.

Executive priority

Treat this as high-priority for affected operational environments. Business urgency depends on whether these devices exist and whether their update or MQTT traffic is exposed to interception.

Technical view

The issue is a CWE-122 heap-based buffer overflow in the OTA Update u-download functionality. The CVE description says specially crafted MQTT payloads can trigger remote code execution, but the attacker must perform a man-in-the-middle attack. CVSS is 9.0 with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to organizations using Sealevel Systems SeaConnect 370W devices running v1.3.34, especially where MQTT or OTA update traffic can be intercepted or manipulated.

Exploitation context

The documented attack condition requires a man-in-the-middle position and crafted MQTT payloads. The bundle marks KEV as false and provides no cited evidence of exploitation in the wild.

Researcher notes

Evidence supports RCE impact through a heap overflow, but exploitation requires MITM conditions. The provided sources do not name a patch, version range beyond v1.3.34, or in-the-wild exploitation.

Mitigation direction

  • Inventory SeaConnect 370W devices and identify firmware v1.3.34.
  • Check Sealevel and Talos guidance for fixed firmware or vendor-approved mitigations.
  • Restrict MQTT and OTA update traffic to trusted, controlled network paths.
  • Reduce man-in-the-middle risk with segmentation and protected management networks.
  • Prioritize isolation if affected devices cannot be updated promptly.

Validation and detection

  • Confirm whether SeaConnect 370W v1.3.34 exists in the environment.
  • Review device network paths for MQTT and OTA update exposure.
  • Check whether untrusted systems can intercept or relay device traffic.
  • Verify remediation status against vendor or Talos guidance.
  • Document compensating controls where firmware status remains unresolved.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-122: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-21962 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9CVSS 3.0CriticalCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H2.26Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

9Critical
CVSS 3.0 vector shape for CVE-2021-21962Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aSealevelSealevel Systems, Inc. SeaConnect 370W v1.3.34Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-122 · source CWE mapping

Heap-based Buffer Overflow

Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.