{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2001-1359 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2001-1359 yet. Limit exposure of the affected software until one is available.","what":"CVE-2001-1359 is a critical vulnerability in n/a, published on 2 Apr 2003. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2001-1359 and fix it if it is affected.\n\nWhat it is: CVE-2001-1359 is a critical vulnerability in n/a, published on 2 Apr 2003. 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-2001-1359 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-1359/ (Markdown: https://insights.sbomify.com/CVE-2001-1359/index.md)","id":"CVE-2001-1359","markdown":"https://insights.sbomify.com/CVE-2001-1359/index.md","name":"CVE-2001-1359","record":{"aliases":["GHSA-rw42-j6r8-j8rw"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Volution client","requires_auth":"none","summary":"Remote attackers can fully control Volution clients by exploiting a fallback mechanism to a Trojan server after LDAP failure.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"volution","vendor":"caldera"}],"cvss":{"score":10,"severity":"critical","source":"nvd","vector":"AV:N/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"Volution clients 1.0.7 and earlier attempt to contact the computer creation daemon (CCD) when an LDAP authentication failure occurs, which allows remote attackers to fully control clients via a Trojan horse Volution server.","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":"Other in n/a","id":"CVE-2001-1359","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2001"},"n_packages":0,"n_references":3,"next":{"headline":"Vulnerability in Scanner Access Now Easy (SANE) before 1.0.5, related to pnm and saned.","id":"CVE-2001-1360"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2001-1358"},"products":["n/a"],"published":"2003-04-02","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-08-08","vendors":["n/a"]},"summary":"Remote attackers can fully control Volution clients by exploiting a fallback mechanism to a Trojan server after LDAP failure.","url":"https://insights.sbomify.com/CVE-2001-1359/"}