{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-25140 exists.","fix":"No fix has been published for CVE-2024-25140 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-25140 is a critical vulnerability in n/a, published on 6 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-25140 and fix it if it is affected.\n\nWhat it is: CVE-2024-25140 is a critical vulnerability in n/a, published on 6 Feb 2024. 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-2024-25140 exists.\n\nAffected product: n/a. 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-2024-25140/ (Markdown: https://insights.sbomify.com/CVE-2024-25140/index.md)","id":"CVE-2024-25140","markdown":"https://insights.sbomify.com/CVE-2024-25140/index.md","name":"CVE-2024-25140","record":{"aliases":["GHSA-xc8c-3cmg-p9qr"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Remote desktop software","requires_auth":"none","summary":"RustDesk installs a test certificate in the trusted root store, potentially allowing arbitrary code execution if the private key is compromised.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rustdesk","vendor":"rustdesk"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"A default installation of RustDesk 1.2.3 on Windows places a WDKTestCert certificate under Trusted Root Certification Authorities with Enhanced Key Usage of Code Signing (1.3.6.1.5.5.7.3.3), valid from 2023 until 2033. This is potentially unwanted, e.g., because there is no public documentation of security measures for the private key, and arbitrary software could be signed if the private key were to be compromised. NOTE: the vendor's position is \"we do not have EV cert, so we use test cert as a workaround.\" Insertion into Trusted Root Certification Authorities was the originally intended behavior, and the UI ensured that the certificate installation step (checked by default) was visible to the user before proceeding with the product installation.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Misconfiguration in n/a","id":"CVE-2024-25140","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Improper Certificate Validation in apache airflow mongo hook","id":"CVE-2024-25141"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2024-25139"},"products":["n/a"],"published":"2024-02-06","related":[{"cvss_score":9.3,"headline":"RustDesk Flutter URI Handler Sets Permanent Password Without Privilege Check or User Confirmation","id":"CVE-2026-30793","kev_date_added":null,"published":"2026-03-05"},{"cvss_score":9.3,"headline":"RustDesk rustdesk://config/ URI Silently Re-homes Client to Attacker-Controlled Server","id":"CVE-2026-30797","kev_date_added":null,"published":"2026-03-05"},{"cvss_score":8.7,"headline":"RustDesk Client Accepts Pseudo-Encrypted Config Strings Without Cryptographic Validation","id":"CVE-2026-30791","kev_date_added":null,"published":"2026-03-05"},{"cvss_score":8.7,"headline":"RustDesk HTTP Client Silently Accepts Invalid TLS Certificates After Handshake Failure","id":"CVE-2026-30795","kev_date_added":null,"published":"2026-03-05"},{"cvss_score":8.3,"headline":"RustDesk Client Blindly Merges Unauthenticated Strategy Payloads, Bypassing Local Security Settings","id":"CVE-2026-30792","kev_date_added":null,"published":"2026-03-05"},{"cvss_score":8.2,"headline":"RustDesk Encrypts Local Passwords with World-Readable Machine ID and Fixed Zero Nonce (XSalsa20-Poly1305)","id":"CVE-2026-30785","kev_date_added":null,"published":"2026-03-05"}],"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-29","vendors":["n/a"]},"summary":"RustDesk installs a test certificate in the trusted root store, potentially allowing arbitrary code execution if the private key is compromised.","url":"https://insights.sbomify.com/CVE-2024-25140/"}