{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-29400 exists.","fix":"No fix has been published for CVE-2024-29400 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-29400 is a high-severity vulnerability in Ruoyi Ruoyi, published on 12 Apr 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-29400 and fix it if it is affected.\n\nWhat it is: CVE-2024-29400 is a high-severity vulnerability in Ruoyi Ruoyi, published on 12 Apr 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-29400 exists.\n\nAffected product: Ruoyi Ruoyi. 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-29400/ (Markdown: https://insights.sbomify.com/CVE-2024-29400/index.md)","id":"CVE-2024-29400","markdown":"https://insights.sbomify.com/CVE-2024-29400/index.md","name":"CVE-2024-29400","record":{"aliases":["GHSA-hh22-pfjg-5xx4"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"RuoYi admin framework","requires_auth":"none","summary":"Attackers can obtain sensitive information via the status parameter in RuoYi, requiring an upgrade to mitigate.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ruoyi","vendor":"ruoyi"}],"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-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An issue was discovered in RuoYi v4.5.1, allows attackers to obtain sensitive information via the status parameter.","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":"Information disclosure in n/a","id":"CVE-2024-29400","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ruoyi:ruoyi","products":["ruoyi:ruoyi"],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in n/a","id":"CVE-2024-29401"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2024-29399"},"products":["n/a"],"published":"2024-04-12","related":[{"cvss_score":10,"headline":"SQL injection in n/a","id":"CVE-2024-57521","kev_date_added":null,"published":"2025-12-23"},{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2025-28402","kev_date_added":null,"published":"2025-04-07"},{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2025-28405","kev_date_added":null,"published":"2025-04-07"},{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2025-28406","kev_date_added":null,"published":"2025-04-07"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2025-28408","kev_date_added":null,"published":"2025-04-07"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2025-28410","kev_date_added":null,"published":"2025-04-07"},{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2025-28411","kev_date_added":null,"published":"2025-04-07"}],"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":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["n/a"]},"summary":"Attackers can obtain sensitive information via the status parameter in RuoYi, requiring an upgrade to mitigate.","url":"https://insights.sbomify.com/CVE-2024-29400/"}