{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-48874 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-48874 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-48874 is a critical server-side request forgery vulnerability in Ruijie Reyee OS, published on 6 Dec 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-48874 and fix it if it is affected.\n\nWhat it is: CVE-2024-48874 is a critical server-side request forgery vulnerability in Ruijie Reyee OS, published on 6 Dec 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-48874 in the wild and no public exploit code.\n\nAffected product: Ruijie Reyee OS. 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-48874/ (Markdown: https://insights.sbomify.com/CVE-2024-48874/index.md)","id":"CVE-2024-48874","markdown":"https://insights.sbomify.com/CVE-2024-48874/index.md","name":"CVE-2024-48874","record":{"aliases":["GHSA-q8f9-449c-rf6m"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Ruijie Reyee OS","requires_auth":"none","summary":"Attackers can force Ruijie proxy servers to make arbitrary requests, accessing internal services and AWS cloud metadata.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"reyee_os","vendor":"ruijienetworks"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Ruijie Reyee OS versions 2.206.x up to but not including 2.320.x could give attackers the ability to force Ruijie's proxy servers to perform any request the attackers choose. Using this, attackers could access internal services used by Ruijie and their internal cloud infrastructure via AWS cloud metadata services.","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":"Ruijie Reyee OS Server-Side Request Forgery","id":"CVE-2024-48874","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"btrfs: don't take dev_replace rwsem on task already holding it","id":"CVE-2024-48875"},"packages":[],"prev":{"headline":"wifi: rtw89: check return value of ieee80211_probereq_get() for RNR","id":"CVE-2024-48873"},"products":["Reyee OS"],"published":"2024-12-06","related":[{"cvss_score":9.3,"headline":"Ruijie Reyee OS Weak Password Recovery Mechanism for Forgotten Password","id":"CVE-2024-47547","kev_date_added":null,"published":"2024-12-06"},{"cvss_score":9.2,"headline":"ReyeeOS 1.204.1614 Man-in-the-Middle Remote Code Execution via CWMP","id":"CVE-2023-53881","kev_date_added":null,"published":"2025-12-15"},{"cvss_score":9.2,"headline":"Ruijie Reyee OS Improper Handling of Insufficient Permissions or Privileges","id":"CVE-2024-46874","kev_date_added":null,"published":"2024-12-06"},{"cvss_score":9.2,"headline":"Ruijie Reyee OS Use of Inherently Dangerous Function","id":"CVE-2024-52324","kev_date_added":null,"published":"2024-12-06"},{"cvss_score":8.7,"headline":"Ruijie Reyee OS Use of Weak Credentials","id":"CVE-2024-45722","kev_date_added":null,"published":"2024-12-06"},{"cvss_score":8.7,"headline":"Ruijie Reyee OS Insecure Storage of Sensitive Information","id":"CVE-2024-47043","kev_date_added":null,"published":"2024-12-06"}],"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":"total"},"state":"PUBLISHED","updated":"2024-12-06","vendors":["Ruijie"]},"summary":"Attackers can force Ruijie proxy servers to make arbitrary requests, accessing internal services and AWS cloud metadata.","url":"https://insights.sbomify.com/CVE-2024-48874/"}