{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-25389 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-25389 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-25389 is a high-severity vulnerability in n/a, published on 27 Mar 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-25389 and fix it if it is affected.\n\nWhat it is: CVE-2024-25389 is a high-severity vulnerability in n/a, published on 27 Mar 2024. 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-2024-25389 in the wild and no public exploit code.\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-25389/ (Markdown: https://insights.sbomify.com/CVE-2024-25389/index.md)","id":"CVE-2024-25389","markdown":"https://insights.sbomify.com/CVE-2024-25389/index.md","name":"CVE-2024-25389","record":{"aliases":["GHSA-6c2g-6j82-6fjx"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"RT-Thread RTOS","requires_auth":"none","summary":"RT-Thread uses a weak random number generator, potentially allowing attackers to predict values and bypass security mechanisms.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rt-thread","vendor":"rt-thread"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"}],"description":"RT-Thread through 5.0.2 generates random numbers with a weak algorithm of \"seed = 214013L * seed + 2531011L; return (seed \u003e\u003e 16) \u0026 0x7FFF;\" in calc_random in drivers/misc/rt_random.c.","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":"Weak cryptography in n/a","id":"CVE-2024-25389","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2024"},"n_packages":0,"n_references":5,"next":{"headline":"Memory corruption in n/a","id":"CVE-2024-25390"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2024-25388"},"products":["n/a"],"published":"2024-03-27","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-04","vendors":["n/a"]},"summary":"RT-Thread uses a weak random number generator, potentially allowing attackers to predict values and bypass security mechanisms.","url":"https://insights.sbomify.com/CVE-2024-25389/"}