{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-12333 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-12333 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-12333 is a high-severity vulnerability in n/a, published on 17 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-12333 and fix it if it is affected.\n\nWhat it is: CVE-2018-12333 is a high-severity vulnerability in n/a, published on 17 Jun 2018. 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-2018-12333 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-12333/ (Markdown: https://insights.sbomify.com/CVE-2018-12333/index.md)","id":"CVE-2018-12333","markdown":"https://insights.sbomify.com/CVE-2018-12333/index.md","name":"CVE-2018-12333","record":{"aliases":["GHSA-qjw9-g27w-ghh4"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Secure Boot Stick","requires_auth":"none","summary":"Attackers can bypass secure boot verification to manipulate configurations and execute malicious code on ECOS Secure Boot Stick devices.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"secure_boot_stick_firmware","vendor":"ecos"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"Insufficient Verification of Data Authenticity vulnerability in ECOS Secure Boot Stick (aka SBS) 5.6.5 allows an attacker to manipulate security relevant configurations and execute malicious code.","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-12333","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":"Security feature bypass in n/a","id":"CVE-2018-12334"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-12332"},"products":["n/a"],"published":"2018-06-17","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2018-12336","kev_date_added":null,"published":"2018-06-17"},{"cvss_score":8.1,"headline":"Security feature bypass in n/a","id":"CVE-2018-12330","kev_date_added":null,"published":"2018-06-17"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2018-12334","kev_date_added":null,"published":"2018-06-17"},{"cvss_score":5.9,"headline":"Security feature bypass in n/a","id":"CVE-2018-12329","kev_date_added":null,"published":"2018-06-17"},{"cvss_score":4.6,"headline":"Information disclosure in n/a","id":"CVE-2018-12337","kev_date_added":null,"published":"2018-06-17"},{"cvss_score":4.2,"headline":"Information disclosure in n/a","id":"CVE-2018-12332","kev_date_added":null,"published":"2018-06-17"}],"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-05","vendors":["n/a"]},"summary":"Attackers can bypass secure boot verification to manipulate configurations and execute malicious code on ECOS Secure Boot Stick devices.","url":"https://insights.sbomify.com/CVE-2018-12333/"}