LiveActive security incident?Get immediate response
CVE Record

CVE-2021-21969: 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 [4] the json_object_get_string to populate the p_payload global variable. The p_payload is only 0x100 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-21969 is a low-severity memory-safety flaw in Sealevel Systems SeaConnect 370W v1.3.34. A specially formed SeaCloud/MQTT message could write outside a small buffer, potentially altering data. Sources do not show public exploitation or a named patch.

Executive priority

Treat this as a targeted hygiene item, not an emergency. Prioritize if affected devices are internet-facing, used in operational environments, or lack network segmentation. The main business action is confirming exposure and vendor-supported remediation options.

Technical view

The HandleIncomingSeaCloudMessage path uses json_object_get_string to copy JSON payload data into the global p_payload buffer. The buffer is 0x100 bytes, while the MQTT message can reach 0x201 bytes, creating an out-of-bounds write. CVSS indicates network access, high attack complexity, no privileges, no user interaction, and low integrity impact.

Likely exposure

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

Exploitation context

The CVE is not listed as KEV, and the supplied sources do not claim active exploitation. Exploitation would require network reachability to the affected message-handling functionality and a high-complexity condition, with impact described as low integrity only.

Researcher notes

The public evidence is specific to SeaConnect 370W v1.3.34 and the HandleSeaCloudMessage path. Do not generalize impact beyond low integrity without additional vendor data. Patch status is not provided in the supplied sources.

Mitigation direction

  • Identify SeaConnect 370W devices and confirm firmware version 1.3.34.
  • Check Sealevel or Talos guidance for fixed firmware or supported mitigation.
  • Restrict device and MQTT/SeaCloud access to trusted management networks.
  • Avoid exposing affected devices directly to the internet.
  • Monitor vendor advisories; plan upgrade or replacement if no supported fix exists.

Validation and detection

  • Inventory OT and IoT assets for Sealevel SeaConnect 370W devices.
  • Verify firmware version from the device interface or asset records.
  • Review firewall rules for SeaCloud or MQTT reachability from untrusted networks.
  • Check vulnerability management records for CVE-2021-21969 coverage.
  • Confirm whether vendor remediation guidance exists before closing the finding.
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-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-21969 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-21969Attack 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/aSealevel"Sealevel 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.