{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-21968 exists.","fix":"No fix has been published for CVE-2021-21968 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-21968 is a high-severity path traversal 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-21968 and fix it if it is affected.\n\nWhat it is: CVE-2021-21968 is a high-severity path traversal 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-21968 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-21968/ (Markdown: https://insights.sbomify.com/CVE-2021-21968/index.md)","id":"CVE-2021-21968","markdown":"https://insights.sbomify.com/CVE-2021-21968/index.md","name":"CVE-2021-21968","record":{"aliases":["GHSA-fmc6-6r82-9j7v"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"SeaConnect 370W","requires_auth":"none","summary":"An attacker can overwrite arbitrary files via a crafted MQTT payload in the OTA update task, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"seaconnect_370w_firmware","vendor":"sealevel"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"A file write vulnerability exists in the OTA update task functionality of Sealevel Systems, Inc. SeaConnect 370W v1.3.34. A specially-crafted MQTT payload can lead to arbitrary file overwrite. 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":"Path traversal in Sealevel","id":"CVE-2021-21968","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Sealevel\"","id":"CVE-2021-21969"},"packages":[],"prev":{"headline":"Memory corruption in SeaConnect 370W","id":"CVE-2021-21967"},"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":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":"total"},"state":"PUBLISHED","updated":"2025-04-15","vendors":["n/a"]},"summary":"An attacker can overwrite arbitrary files via a crafted MQTT payload in the OTA update task, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2021-21968/"}