{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-20960 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-20960 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-20960 is a high-severity vulnerability in n/a, published on 8 Aug 2019. 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-2018-20960 and fix it if it is affected.\n\nWhat it is: CVE-2018-20960 is a high-severity vulnerability in n/a, published on 8 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-20960 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-2018-20960/ (Markdown: https://insights.sbomify.com/CVE-2018-20960/index.md)","id":"CVE-2018-20960","markdown":"https://insights.sbomify.com/CVE-2018-20960/index.md","name":"CVE-2018-20960","record":{"aliases":["GHSA-6g3v-2r46-2fvm"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Nespresso coffee machine","requires_auth":"none","summary":"Nespresso Prodigio devices lack Bluetooth connection security, allowing attackers to bypass authentication mechanisms.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"prodigo_firmware","vendor":"nespresso"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H","version":"3.0"},"cwes":[],"description":"Nespresso Prodigio devices lack Bluetooth connection security.","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-2018-20960","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Use after free in n/a","id":"CVE-2018-20961"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2018-20959"},"products":["n/a"],"published":"2019-08-08","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-05","vendors":["n/a"]},"summary":"Nespresso Prodigio devices lack Bluetooth connection security, allowing attackers to bypass authentication mechanisms.","url":"https://insights.sbomify.com/CVE-2018-20960/"}