VYPR
Unrated severityNVD Advisory· Published Feb 4, 2022· Updated Apr 15, 2025

CVE-2021-21969

CVE-2021-21969

Description

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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Out-of-bounds write in SeaConnect 370W v1.3.34 allows man-in-the-middle attacker to cause buffer overflow via crafted MQTT message.

Vulnerability

An out-of-bounds write vulnerability exists in the HandleSeaCloudMessage functionality of Sealevel Systems, Inc. SeaConnect 370W v1.3.34. The HandleIncomingSeaCloudMessage function uses json_object_get_string to populate the global variable p_payload, which is only 0x100 bytes long. However, the total incoming MQTT message can be up to 0x201 bytes. Because json_object_get_string fills the buffer based on the JSON value length rather than the buffer size, this leads to a potential out-of-bounds write [1].

Exploitation

An attacker with a man-in-the-middle (MITM) position can send a specially-crafted MQTT payload to the device's subscribed topic. No authentication is required (CVSS PR:N). The device receives and parses the JSON-formatted message, copying the "payload" field into the fixed-size buffer without any size check, thereby overwriting adjacent memory [1].

Impact

Successful exploitation results in an out-of-bounds write, which can corrupt memory and potentially cause a denial of service or, in more severe cases, lead to code execution. The CVSSv3 score of 3.7 (low) indicates limited impact on integrity (partial) with no direct impact on confidentiality or availability [1].

Mitigation

As of the publication date, no patch has been released by Sealevel Systems. Users should monitor vendor updates for a fix. As a workaround, restrict network access to the device, use encrypted communication channels (e.g., TLS for MQTT), and employ network segmentation to reduce the risk of MITM attacks [1].

AI Insight generated on May 25, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

1

News mentions

0

No linked articles in our index yet.