LiveActive security incident?Get immediate response
CVE Record

CVE-2021-21970: An out-of-bounds write vulnerability exists in the HandleSeaCloudMessage functionality of Sealevel Systems,...

An out-of-bounds write vulnerability exists in the HandleSeaCloudMessage functionality of Sealevel Systems, Inc. SeaConnect 370W v1.3.34. The HandleIncomingSeaCloudMessage function uses at [3] the json_object_get_string to populate the p_name global variable. The p_name is only 0x80 bytes long, and the total MQTT message could be up to 0x201 bytes. Because the function json_object_get_string will fill str based on the length of the json’s value and not the actual str size, this would result in a possible out-of-bounds write.

LowCVSS 3.7Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2021-21970 affects Sealevel Systems SeaConnect 370W v1.3.34. A network message processed by the device can write more data than a small name buffer can hold. Published scoring rates impact as low: integrity only, high attack complexity, no user interaction, and no privileges required.

Executive priority

Handle as a targeted operational technology exposure issue, not an enterprise-wide emergency. Prioritize if these devices are internet-exposed or reachable from less-trusted networks. Otherwise, manage through normal firmware and segmentation processes.

Technical view

Talos describes an out-of-bounds write in HandleIncomingSeaCloudMessage/HandleSeaCloudMessage. json_object_get_string populates global p_name, sized 0x80 bytes, from a JSON value in an MQTT message that may be up to 0x201 bytes. The CVSS vector is network, high complexity, no privileges, no user interaction, integrity low.

Likely exposure

Exposure is likely limited to organizations using Sealevel Systems SeaConnect 370W devices on firmware v1.3.34, especially where MQTT or SeaCloud messaging is reachable from untrusted networks. The source bundle does not identify other affected versions or products.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not listed as KEV. The CVSS vector indicates remote reachability but high attack complexity. Treat exploitation as plausible in exposed environments, not confirmed in the wild.

Researcher notes

Evidence is narrow and specific: SeaConnect 370W v1.3.34, CWE-120, MQTT JSON handling, p_name buffer overflow condition. No source in the bundle confirms code execution, public exploitation, a patch level, or affected-version range beyond v1.3.34.

Mitigation direction

  • Inventory SeaConnect 370W devices and identify firmware v1.3.34.
  • Check Sealevel and Talos guidance for fixed firmware or vendor mitigations.
  • Restrict device messaging interfaces to trusted networks and brokers.
  • Block direct internet exposure for affected devices where possible.
  • Monitor device messaging paths for unexpected or malformed traffic.

Validation and detection

  • Confirm whether SeaConnect 370W v1.3.34 exists in asset inventory.
  • Verify MQTT or SeaCloud messaging reachability from untrusted networks.
  • Review network controls around the device and broker paths.
  • Check vendor support channels for fixed firmware availability.
  • Document affected assets, compensating controls, and remediation status.
Prepared
Confidence
high
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-120: 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
cve · low confidence lookup

CVE-2021-21970 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
Low
CVSS
3.7 (3.0)
Known Exploited
No
Published

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

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
3.7CVSS 3.0LowCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N2.21.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

3.7Low
CVSS 3.0 vector shape for CVE-2021-21970Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.