{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-6693 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-6693 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-6693 is a high-severity memory corruption vulnerability in RT-Thread, published on 26 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-6693 and fix it if it is affected.\n\nWhat it is: CVE-2025-6693 is a high-severity memory corruption vulnerability in RT-Thread, published on 26 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-6693 in the wild and no public exploit code.\n\nAffected product: RT-Thread. 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-2025-6693/ (Markdown: https://insights.sbomify.com/CVE-2025-6693/index.md)","id":"CVE-2025-6693","markdown":"https://insights.sbomify.com/CVE-2025-6693/index.md","name":"CVE-2025-6693","record":{"aliases":["GHSA-mq4w-gr2r-39x4"],"analysis":{"component_type":"operating_system","fix_type":"no_fix_stated","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"RT-Thread RTOS","requires_auth":"low_privilege","summary":"Local attackers can exploit memory corruption in RT-Thread device drivers to potentially execute arbitrary code or escalate privileges.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"rt-thread","vendor":"rt-thread"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X","version":"4.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"A vulnerability, which was classified as critical, was found in RT-Thread up to 5.1.0. This affects the function sys_device_open/sys_device_read/sys_device_control/sys_device_init/sys_device_close/sys_device_write of the file components/drivers/core/device.c. The manipulation leads to memory corruption. It is possible to launch the attack on the local host. The vendor was contacted early about this disclosure but did not respond in any way.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"RT-Thread device.c sys_device_write memory corruption","id":"CVE-2025-6693","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":9,"next":{"headline":"LabRedesCefetRJ WeGIA Adicionar Unidade adicionar_unidade.php cross site scripting","id":"CVE-2025-6694"},"packages":[],"prev":{"headline":"YouTube Embed \u003c= 10.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via instance Parameter","id":"CVE-2025-6692"},"products":["RT-Thread"],"published":"2025-06-26","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-25393","kev_date_added":null,"published":"2024-03-27"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2024-25395","kev_date_added":null,"published":"2024-03-27"},{"cvss_score":8.6,"headline":"RT-Thread Parameter lwp_syscall.c sys_select memory corruption","id":"CVE-2025-5865","kev_date_added":null,"published":"2025-06-09"},{"cvss_score":8.6,"headline":"RT-Thread lwp_syscall.c sys_sigprocmask array index","id":"CVE-2025-5866","kev_date_added":null,"published":"2025-06-09"},{"cvss_score":8.6,"headline":"RT-Thread lwp_syscall.c csys_sendto null pointer dereference","id":"CVE-2025-5867","kev_date_added":null,"published":"2025-06-09"},{"cvss_score":8.6,"headline":"RT-Thread lwp_syscall.c sys_thread_sigprocmask array index","id":"CVE-2025-5868","kev_date_added":null,"published":"2025-06-09"},{"cvss_score":8.6,"headline":"RT-Thread lwp_syscall.c sys_recvfrom memory corruption","id":"CVE-2025-5869","kev_date_added":null,"published":"2025-06-09"}],"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-06-26","vendors":["n/a"]},"summary":"Local attackers can exploit memory corruption in RT-Thread device drivers to potentially execute arbitrary code or escalate privileges.","url":"https://insights.sbomify.com/CVE-2025-6693/"}