{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2001-1536 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2001-1536 yet. Limit exposure of the affected software until one is available.","what":"CVE-2001-1536 is a high-severity vulnerability in n/a, published on 14 Jul 2005. 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-1536 and fix it if it is affected.\n\nWhat it is: CVE-2001-1536 is a high-severity vulnerability in n/a, published on 14 Jul 2005. 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-1536 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-1536/ (Markdown: https://insights.sbomify.com/CVE-2001-1536/index.md)","id":"CVE-2001-1536","markdown":"https://insights.sbomify.com/CVE-2001-1536/index.md","name":"CVE-2001-1536","record":{"aliases":["GHSA-gqm3-6h45-q66x"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Autogalaxy web app","requires_auth":"none","summary":"Autogalaxy stores credentials in cleartext cookies, allowing attackers to steal authentication data via sniffing or XSS.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"audiogalaxy","vendor":"audiogalaxy"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"Autogalaxy stores usernames and passwords in cleartext in cookies, which makes it easier for remote attackers to obtain authentication information and gain unauthorized access via sniffing or a cross-site scripting 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":"Information disclosure in n/a","id":"CVE-2001-1536","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2001"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2001-1537"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2001-1535"},"products":["n/a"],"published":"2005-07-14","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["n/a"]},"summary":"Autogalaxy stores credentials in cleartext cookies, allowing attackers to steal authentication data via sniffing or XSS.","url":"https://insights.sbomify.com/CVE-2001-1536/"}