{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-1106 exists.","fix":"No fix has been published for CVE-2001-1106 yet. Limit exposure of the affected software until one is available.","what":"CVE-2001-1106 is a high-severity vulnerability in n/a, published on 2 Apr 2003. 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-1106 and fix it if it is affected.\n\nWhat it is: CVE-2001-1106 is a high-severity vulnerability in n/a, published on 2 Apr 2003. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-1106 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-2001-1106/ (Markdown: https://insights.sbomify.com/CVE-2001-1106/index.md)","id":"CVE-2001-1106","markdown":"https://insights.sbomify.com/CVE-2001-1106/index.md","name":"CVE-2001-1106","record":{"aliases":["GHSA-wwvp-6w6m-5m73"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["data_read","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Sambar Web Server","requires_auth":"low_privilege","summary":"Local attackers can decrypt all user passwords by exploiting a hardcoded symmetric key in the Sambar Server binary.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sambar_server","vendor":"sambar"}],"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 default configuration of Sambar Server 5 and earlier uses a symmetric key that is compiled into the binary program for encrypting passwords, which could allow local users to break all user passwords by cracking the key or modifying a copy of the sambar program to call the decryption procedure.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2001-07-25","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2001-07-25","kind":"exploitdb","ref":"21027","stars":null,"title":"Sambar Server 4.x/5.0 - Insecure Default Password Protection"}],"tier":"weaponised"},"has_fix":null,"headline":"Weak cryptography in n/a","id":"CVE-2001-1106","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2001"},"n_packages":0,"n_references":3,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2001-1107"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2001-1105"},"products":["n/a"],"published":"2003-04-02","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2000-0509","kev_date_added":null,"published":"2000-07-12"},{"cvss_score":7.5,"headline":"Server-side request forgery in n/a","id":"CVE-2003-1286","kev_date_added":null,"published":"2005-11-22"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2002-0128","kev_date_added":null,"published":"2002-06-25"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2001-1292","kev_date_added":null,"published":"2002-05-03"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-1999-1523","kev_date_added":null,"published":"2001-09-12"},{"cvss_score":6.4,"headline":"Information disclosure in n/a","id":"CVE-2002-0737","kev_date_added":null,"published":"2003-04-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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Local attackers can decrypt all user passwords by exploiting a hardcoded symmetric key in the Sambar Server binary.","url":"https://insights.sbomify.com/CVE-2001-1106/"}