{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15501 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-15501 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-15501 is a medium-severity vulnerability in n/a, published on 7 Oct 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-15501 and fix it if it is affected.\n\nWhat it is: CVE-2020-15501 is a medium-severity vulnerability in n/a, published on 7 Oct 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-15501 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-2020-15501/ (Markdown: https://insights.sbomify.com/CVE-2020-15501/index.md)","id":"CVE-2020-15501","markdown":"https://insights.sbomify.com/CVE-2020-15501/index.md","name":"CVE-2020-15501","record":{"aliases":["GHSA-rj25-mh3f-7r6m"],"analysis":{"component_type":"iot_embedded","fix_type":"end_of_life","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Smart coffee maker","requires_auth":"none","summary":"Attackers can replace firmware without authentication on unsupported first-generation Smarter Coffee Makers, requiring physical button press.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"smarter_coffee_maker_1st_generation","vendor":"smarter"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[],"description":"Smarter Coffee Maker before 2nd generation allows firmware replacement without authentication or authorization. User interaction is required to press a button. NOTE: This vulnerability only affects products that are no longer supported by the maintainer","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":"Security feature bypass in n/a","id":"CVE-2020-15501","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2020-15502"},"packages":[],"prev":{"headline":"Cross-site scripting in TileServer GL","id":"CVE-2020-15500"},"products":["n/a"],"published":"2020-10-07","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-04","vendors":["n/a"]},"summary":"Attackers can replace firmware without authentication on unsupported first-generation Smarter Coffee Makers, requiring physical button press.","url":"https://insights.sbomify.com/CVE-2020-15501/"}