{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2001-1007 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2001-1007 yet. Limit exposure of the affected software until one is available.","what":"CVE-2001-1007 is a medium-severity vulnerability in n/a, published on 2 Feb 2002. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2001-1007 and fix it if it is affected.\n\nWhat it is: CVE-2001-1007 is a medium-severity vulnerability in n/a, published on 2 Feb 2002. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2001-1007 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-2001-1007/ (Markdown: https://insights.sbomify.com/CVE-2001-1007/index.md)","id":"CVE-2001-1007","markdown":"https://insights.sbomify.com/CVE-2001-1007/index.md","name":"CVE-2001-1007","record":{"aliases":["GHSA-497x-28hv-cvv5"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"PDA synchronization software","requires_auth":"none","summary":"Attackers can brute-force device keys quickly due to a small keyspace and lack of delay, bypassing synchronization security on REX 5000 PDAs.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"truesync_desktop","vendor":"starfish"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:N/A:P","version":"2.0"},"cwes":[],"description":"Starfish Truesync Desktop 2.0b as used on the REX 5000 PDA uses a small keyspace for device keys and does not impose a delay when an incorrect key is entered, which allows attackers to more quickly guess the key via a brute force attack.","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":"Weak cryptography in n/a","id":"CVE-2001-1007","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2001"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2001-1008"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2001-1006"},"products":["n/a"],"published":"2002-02-02","related":[{"cvss_score":7.5,"headline":"Weak cryptography in n/a","id":"CVE-2001-1005","kev_date_added":null,"published":"2002-02-02"},{"cvss_score":5,"headline":"Information disclosure in n/a","id":"CVE-2001-1006","kev_date_added":null,"published":"2002-02-02"}],"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-08","vendors":["n/a"]},"summary":"Attackers can brute-force device keys quickly due to a small keyspace and lack of delay, bypassing synchronization security on REX 5000 PDAs.","url":"https://insights.sbomify.com/CVE-2001-1007/"}