{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15085 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-15085 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-15085 is a medium-severity vulnerability in mirumee saleor-storefront, published on 30 Jun 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-15085 and fix it if it is affected.\n\nWhat it is: CVE-2020-15085 is a medium-severity vulnerability in mirumee saleor-storefront, published on 30 Jun 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-15085 in the wild and no public exploit code.\n\nAffected product: mirumee saleor-storefront. 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-2020-15085/ (Markdown: https://insights.sbomify.com/CVE-2020-15085/index.md)","id":"CVE-2020-15085","markdown":"https://insights.sbomify.com/CVE-2020-15085/index.md","name":"CVE-2020-15085","record":{"aliases":["GHSA-4279-h39w-2jqm"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Saleor Storefront","requires_auth":"none","summary":"Attackers with local browser access can extract plaintext credentials from cached login data in Saleor Storefront, leading to potential account takeover.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"saleor","vendor":"mirumee"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"In Saleor Storefront before version 2.10.3, request data used to authenticate customers was inadvertently cached in the browser's local storage mechanism, including credentials. A malicious user with direct access to the browser could extract the email and password. In versions prior to 2.10.0 persisted the cache even after the user logged out. This is fixed in version 2.10.3. A workaround is to manually clear application data (browser's local storage) after logging into Saleor Storefront.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Client caching login operation with plaintext password in Saleor Storefront","id":"CVE-2020-15085","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Potential Remote Code Execution in TYPO3 with mediace extension","id":"CVE-2020-15086"},"packages":[],"prev":{"headline":"Authorization bypass in express-jwt","id":"CVE-2020-15084"},"products":["saleor-storefront"],"published":"2020-06-30","related":[{"cvss_score":8.8,"headline":"Mirumee Saleor CSRF Protection Disabled","id":"CVE-2019-13594","kev_date_added":null,"published":"2019-07-14"},{"cvss_score":5.3,"headline":"Missing Authentication for Critical Function in Saleor","id":"CVE-2020-7964","kev_date_added":null,"published":"2020-01-24"},{"cvss_score":5.3,"headline":"Missing authorization in Saleor","id":"CVE-2019-1010304","kev_date_added":null,"published":"2019-07-15"}],"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-08-04","vendors":["mirumee"]},"summary":"Attackers with local browser access can extract plaintext credentials from cached login data in Saleor Storefront, leading to potential account takeover.","url":"https://insights.sbomify.com/CVE-2020-15085/"}