{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-0745 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-0745 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-0745 is a medium-severity vulnerability in n/a, published on 13 Mar 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2005-0745 and fix it if it is affected.\n\nWhat it is: CVE-2005-0745 is a medium-severity vulnerability in n/a, published on 13 Mar 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2005-0745 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-0745/ (Markdown: https://insights.sbomify.com/CVE-2005-0745/index.md)","id":"CVE-2005-0745","markdown":"https://insights.sbomify.com/CVE-2005-0745/index.md","name":"CVE-2005-0745","record":{"aliases":["GHSA-qfmj-wfcp-vm5p"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"VoIP Analog Terminal Adaptor","requires_auth":"none","summary":"Local users can bypass access restrictions on UTStarcom VoIP ATAs by dialing a specific code to reset the device.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ian-02ex_voip_ata","vendor":"utstarcom"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"UTStarcom iAN-02EX VoIP Analog Terminal Adaptor (ATA) allows local users to bypass ATA access restrictions by dialing \"*#26845#\" and causing a device reset.","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":"Security feature bypass in n/a","id":"CVE-2005-0745","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2005"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2005-0746"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2005-0744"},"products":["n/a"],"published":"2005-03-13","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"Local users can bypass access restrictions on UTStarcom VoIP ATAs by dialing a specific code to reset the device.","url":"https://insights.sbomify.com/CVE-2005-0745/"}