{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55624 exists.","fix":"No fix has been published for CVE-2025-55624 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-55624 is a medium-severity vulnerability in n/a, published on 22 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-55624 and fix it if it is affected.\n\nWhat it is: CVE-2025-55624 is a medium-severity vulnerability in n/a, published on 22 Aug 2025. 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-2025-55624 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-2025-55624/ (Markdown: https://insights.sbomify.com/CVE-2025-55624/index.md)","id":"CVE-2025-55624","markdown":"https://insights.sbomify.com/CVE-2025-55624/index.md","name":"CVE-2025-55624","record":{"aliases":["GHSA-3rv5-c9qq-6335"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Reolink camera firmware","requires_auth":"none","summary":"Attackers can redirect intents to access internal functions or non-public components in Reolink devices, bypassing security controls.","user_interaction":"not_required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"reolink","vendor":"reolink"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"description":"An intent redirection vulnerability in Reolink v4.54.0.4.20250526 allows unauthorized attackers to access internal functions or access non-public components.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Open redirect in n/a","id":"CVE-2025-55624","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"open_redirect","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Open redirect in n/a","id":"CVE-2025-55625"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2025-55623"},"products":["n/a"],"published":"2025-08-22","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-55619","kev_date_added":null,"published":"2025-08-22"},{"cvss_score":6.5,"headline":"Command injection in n/a","id":"CVE-2025-56799","kev_date_added":null,"published":"2025-10-21"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2025-55621","kev_date_added":null,"published":"2025-08-22"},{"cvss_score":6.5,"headline":"Other in n/a","id":"CVE-2025-55622","kev_date_added":null,"published":"2025-08-22"},{"cvss_score":6.3,"headline":"Open redirect in n/a","id":"CVE-2025-55625","kev_date_added":null,"published":"2025-08-22"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2025-55620","kev_date_added":null,"published":"2025-08-22"},{"cvss_score":5.4,"headline":"Auth bypass in n/a","id":"CVE-2025-55623","kev_date_added":null,"published":"2025-08-22"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-22","vendors":["n/a"]},"summary":"Attackers can redirect intents to access internal functions or non-public components in Reolink devices, bypassing security controls.","url":"https://insights.sbomify.com/CVE-2025-55624/"}