{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-3717 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-3717 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-3717 is a high-severity vulnerability in n/a, published on 21 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2005-3717 and fix it if it is affected.\n\nWhat it is: CVE-2005-3717 is a high-severity vulnerability in n/a, published on 21 Nov 2005. 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-2005-3717 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-2005-3717/ (Markdown: https://insights.sbomify.com/CVE-2005-3717/index.md)","id":"CVE-2005-3717","markdown":"https://insights.sbomify.com/CVE-2005-3717/index.md","name":"CVE-2005-3717","record":{"aliases":["GHSA-rxv3-9c28-c2h7"],"analysis":{"component_type":"iot_embedded","fix_type":"configuration_change","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"VOIP WIFI Phone","requires_auth":"none","summary":"Remote attackers can gain full system access to UTStarcom VOIP phones using default hardcoded credentials.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"f1000_voip_wifi_phone","vendor":"utstarcom"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"The telnet daemon in UTStarcom F1000 VOIP WIFI Phone s2.0 running VxWorks 5.5.1 with kernel WIND 2.6 has a default username \"target\" and password \"password\", which allows remote attackers to gain full access to the system.","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-2005-3717","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2005"},"n_packages":0,"n_references":4,"next":{"headline":"Misconfiguration in n/a","id":"CVE-2005-3718"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2005-3716"},"products":["n/a"],"published":"2005-11-21","related":[{"cvss_score":7.5,"headline":"Misconfiguration in n/a","id":"CVE-2005-3718","kev_date_added":null,"published":"2005-11-21"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can gain full system access to UTStarcom VOIP phones using default hardcoded credentials.","url":"https://insights.sbomify.com/CVE-2005-3717/"}