{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-21971 exists.","fix":"No fix has been published for CVE-2021-21971 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-21971 is a low-severity memory corruption vulnerability in Sealevel, published on 4 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-21971 and fix it if it is affected.\n\nWhat it is: CVE-2021-21971 is a low-severity memory corruption vulnerability in Sealevel, published on 4 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-21971 exists.\n\nAffected product: Sealevel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-21971/ (Markdown: https://insights.sbomify.com/CVE-2021-21971/index.md)","id":"CVE-2021-21971","markdown":"https://insights.sbomify.com/CVE-2021-21971/index.md","name":"CVE-2021-21971","record":{"aliases":["GHSA-3975-hvrj-7hm8"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"SeaConnect 370W","requires_auth":"none","summary":"An attacker can trigger an out-of-bounds write in the URL decoder via a crafted MQTT payload, potentially leading to code execution on the device.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"seaconnect_370w_firmware","vendor":"sealevel"}],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"An out-of-bounds write vulnerability exists in the URL_decode functionality of Sealevel Systems, Inc. SeaConnect 370W v1.3.34. A specially-crafted MQTT payload can lead to an out-of-bounds write. An attacker can perform a man-in-the-middle attack to trigger this vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in Sealevel","id":"CVE-2021-21971","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"VMware vCenter Server Remote Code Execution","id":"CVE-2021-21972"},"packages":[],"prev":{"headline":"Memory corruption in Sealevel","id":"CVE-2021-21970"},"products":["Sealevel"],"published":"2022-02-04","related":[{"cvss_score":10,"headline":"Memory corruption in Sealevel","id":"CVE-2021-21960","kev_date_added":null,"published":"2022-02-04"},{"cvss_score":10,"headline":"Memory corruption in Sealevel","id":"CVE-2021-21961","kev_date_added":null,"published":"2022-02-04"},{"cvss_score":9,"headline":"Memory corruption in Sealevel","id":"CVE-2021-21962","kev_date_added":null,"published":"2022-02-04"},{"cvss_score":8.6,"headline":"Denial of service in Sealevel","id":"CVE-2021-21964","kev_date_added":null,"published":"2022-02-04"},{"cvss_score":8.6,"headline":"Denial of service in Sealevel","id":"CVE-2021-21965","kev_date_added":null,"published":"2022-02-04"},{"cvss_score":8.1,"headline":"Path traversal in Sealevel","id":"CVE-2021-21968","kev_date_added":null,"published":"2022-02-04"},{"cvss_score":7.7,"headline":"Misconfiguration in Sealevel","id":"CVE-2021-21959","kev_date_added":null,"published":"2022-02-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-15","vendors":["n/a"]},"summary":"An attacker can trigger an out-of-bounds write in the URL decoder via a crafted MQTT payload, potentially leading to code execution on the device.","url":"https://insights.sbomify.com/CVE-2021-21971/"}