{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2001-1159 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2001-1159 yet. Limit exposure of the affected software until one is available.","what":"CVE-2001-1159 is a high-severity vulnerability in Squirrelmail Squirrelmail, published on 15 Mar 2002. 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-1159 and fix it if it is affected.\n\nWhat it is: CVE-2001-1159 is a high-severity vulnerability in Squirrelmail Squirrelmail, published on 15 Mar 2002. 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-1159 in the wild and no public exploit code.\n\nAffected product: Squirrelmail Squirrelmail. 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-1159/ (Markdown: https://insights.sbomify.com/CVE-2001-1159/index.md)","id":"CVE-2001-1159","markdown":"https://insights.sbomify.com/CVE-2001-1159/index.md","name":"CVE-2001-1159","record":{"aliases":["GHSA-frq8-jv9p-q5hg"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"SquirrelMail webmail","requires_auth":"none","summary":"Remote attackers can execute arbitrary code or view sensitive files in SquirrelMail due to improper variable initialization and file upload flaws.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"squirrelmail","vendor":"squirrelmail"}],"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":"load_prefs.php and supporting include files in SquirrelMail 1.0.4 and earlier do not properly initialize certain PHP variables, which allows remote attackers to (1) view sensitive files via the config_php and data_dir options, and (2) execute arbitrary code by using options_order.php to upload a message that could be interpreted as PHP.","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":"File upload in n/a","id":"CVE-2001-1159","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"squirrelmail:squirrelmail","products":["squirrelmail:squirrelmail"],"type":"file_upload","year":"2001"},"n_packages":0,"n_references":4,"next":{"headline":"Command injection in n/a","id":"CVE-2001-1160"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2001-1158"},"products":["n/a"],"published":"2002-03-15","related":[{"cvss_score":10,"headline":"Command injection in n/a","id":"CVE-2002-0516","kev_date_added":null,"published":"2003-04-02"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2020-14932","kev_date_added":null,"published":"2020-06-20"},{"cvss_score":8.8,"headline":"Deserialization in n/a","id":"CVE-2020-14933","kev_date_added":null,"published":"2020-06-20"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2017-7692","kev_date_added":null,"published":"2017-04-20"},{"cvss_score":7.5,"headline":"Cross-site request forgery in n/a","id":"CVE-2007-2631","kev_date_added":null,"published":"2007-05-13"},{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2006-2842","kev_date_added":null,"published":"2006-06-06"},{"cvss_score":7.5,"headline":"Cross-site request forgery in n/a","id":"CVE-2002-1648","kev_date_added":null,"published":"2005-03-28"}],"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 execute arbitrary code or view sensitive files in SquirrelMail due to improper variable initialization and file upload flaws.","url":"https://insights.sbomify.com/CVE-2001-1159/"}