{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-3710 exists.","fix":"No fix has been published for CVE-2009-3710 yet. Limit exposure of the affected software until one is available.","what":"CVE-2009-3710 is a critical vulnerability in n/a, published on 16 Oct 2009. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2009-3710 and fix it if it is affected.\n\nWhat it is: CVE-2009-3710 is a critical vulnerability in n/a, published on 16 Oct 2009. 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-2009-3710 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-2009-3710/ (Markdown: https://insights.sbomify.com/CVE-2009-3710/index.md)","id":"CVE-2009-3710","markdown":"https://insights.sbomify.com/CVE-2009-3710/index.md","name":"CVE-2009-3710","record":{"aliases":["GHSA-jgv9-qp9j-c2cr"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"RioRey RIOS","requires_auth":"none","summary":"Remote attackers can gain privileges via SSH using hard-coded credentials in RioRey RIOS network devices.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rios","vendor":"riorey"}],"cvss":{"score":10,"severity":"critical","source":"nvd","vector":"AV:N/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[{"id":"CWE-255","name":null}],"description":"RioRey RIOS 4.6.6 and 4.7.0 uses an undocumented, hard-coded username (dbadmin) and password (sq!us3r) for an SSH tunnel, which allows remote attackers to gain privileges via port 8022.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2009-10-08","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2009-10-08","kind":"exploitdb","ref":"9858","stars":null,"title":"Riorey RIOS 4.7.0 - Hard-Coded Password"}],"tier":"weaponised"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2009-3710","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2009"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2009-3711"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2009-3709"},"products":["n/a"],"published":"2009-10-16","related":[],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"Remote attackers can gain privileges via SSH using hard-coded credentials in RioRey RIOS network devices.","url":"https://insights.sbomify.com/CVE-2009-3710/"}