{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-41989 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-41989 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-41989 is a critical memory corruption vulnerability in Sewio RTLS Studio, published on 18 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-41989 and fix it if it is affected.\n\nWhat it is: CVE-2022-41989 is a critical memory corruption vulnerability in Sewio RTLS Studio, published on 18 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-41989 in the wild and no public exploit code.\n\nAffected product: Sewio RTLS Studio. 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-2022-41989/ (Markdown: https://insights.sbomify.com/CVE-2022-41989/index.md)","id":"CVE-2022-41989","markdown":"https://insights.sbomify.com/CVE-2022-41989/index.md","name":"CVE-2022-41989","record":{"aliases":["GHSA-c99p-c624-4w53"],"analysis":{"component_type":"ics_ot","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"RTLS Studio","requires_auth":"none","summary":"An attacker can send an excessively long RTLS report payload to trigger an out-of-bounds write, leading to denial of service or arbitrary code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"real-time_location_system_studio","vendor":"sewio"}],"cvss":{"score":9,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Sewio’s Real-Time Location System (RTLS) Studio version 2.0.0 up to and including version 2.6.2 does not validate the length of RTLS report payloads during communication. This allows an attacker to send an exceedingly long payload, resulting in an out-of-bounds write to cause a denial-of-service condition or code execution.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"CVE-2022-41989","id":"CVE-2022-41989","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress 3D Tag Cloud Plugin \u003c= 3.8 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2022-41990"},"packages":[],"prev":{"headline":"Information disclosure in OpenImageIO","id":"CVE-2022-41988"},"products":["RTLS Studio"],"published":"2023-01-18","related":[{"cvss_score":10,"headline":"CVE-2022-45444","id":"CVE-2022-45444","kev_date_added":null,"published":"2023-01-18"},{"cvss_score":9.1,"headline":"CVE-2022-43483","id":"CVE-2022-43483","kev_date_added":null,"published":"2023-01-18"},{"cvss_score":9.1,"headline":"CVE-2022-47911","id":"CVE-2022-47911","kev_date_added":null,"published":"2023-01-18"},{"cvss_score":8.1,"headline":"CVE-2022-45127","id":"CVE-2022-45127","kev_date_added":null,"published":"2023-01-18"},{"cvss_score":8.1,"headline":"CVE-2022-47395","id":"CVE-2022-47395","kev_date_added":null,"published":"2023-01-18"},{"cvss_score":6.8,"headline":"CVE-2022-47917","id":"CVE-2022-47917","kev_date_added":null,"published":"2023-01-18"}],"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-16","vendors":["Sewio"]},"summary":"An attacker can send an excessively long RTLS report payload to trigger an out-of-bounds write, leading to denial of service or arbitrary code execution.","url":"https://insights.sbomify.com/CVE-2022-41989/"}