{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-25560 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-25560 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-25560 is a critical vulnerability in n/a, published on 11 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-25560 and fix it if it is affected.\n\nWhat it is: CVE-2020-25560 is a critical vulnerability in n/a, published on 11 Aug 2021. 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-2020-25560 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-2020-25560/ (Markdown: https://insights.sbomify.com/CVE-2020-25560/index.md)","id":"CVE-2020-25560","markdown":"https://insights.sbomify.com/CVE-2020-25560/index.md","name":"CVE-2020-25560","record":{"aliases":["GHSA-wjw3-27pj-fvhg"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"SapphireIMS","requires_auth":"none","summary":"Attackers can use hardcoded credentials to access the portal and execute arbitrary OS commands via injection in network tools.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sapphireims","vendor":"sapphireims"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","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-798","name":"Use of Hard-coded Credentials"}],"description":"In SapphireIMS 5.0, it is possible to use the hardcoded credential in clients (username: sapphire, password: ims) and gain access to the portal. Once the access is available, the attacker can inject malicious OS commands on “ping”, “traceroute” and “snmp” functions and execute code on the server. We also observed the same is true if the JSESSIONID is completely removed.","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":"Hardcoded credentials in n/a","id":"CVE-2020-25560","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2020-25561"},"packages":[],"prev":{"headline":"Use after free in n/a","id":"CVE-2020-25559"},"products":["n/a"],"published":"2021-08-11","related":[{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2020-25563","kev_date_added":null,"published":"2021-08-11"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-25565","kev_date_added":null,"published":"2021-08-11"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2020-25566","kev_date_added":null,"published":"2021-08-11"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2017-16630","kev_date_added":null,"published":"2021-08-11"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2020-25564","kev_date_added":null,"published":"2021-08-11"},{"cvss_score":7.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-25561","kev_date_added":null,"published":"2021-08-11"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can use hardcoded credentials to access the portal and execute arbitrary OS commands via injection in network tools.","url":"https://insights.sbomify.com/CVE-2020-25560/"}