{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-12337 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-12337 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-12337 is a medium-severity vulnerability in n/a, published on 17 Jun 2018. 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-12337 and fix it if it is affected.\n\nWhat it is: CVE-2018-12337 is a medium-severity vulnerability in n/a, published on 17 Jun 2018. 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-12337 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-12337/ (Markdown: https://insights.sbomify.com/CVE-2018-12337/index.md)","id":"CVE-2018-12337","markdown":"https://insights.sbomify.com/CVE-2018-12337/index.md","name":"CVE-2018-12337","record":{"aliases":["GHSA-g93m-4fg8-3926"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Secure Boot Stick","requires_auth":"none","summary":"An attacker can partially extract confidential configurations from the ECOS Secure Boot Stick via user-space emulation, exposing sensitive settings.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"secure_boot_stick_firmware","vendor":"ecos"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Reliance on Security Through Obscurity vulnerability in ECOS Secure Boot Stick (aka SBS) 5.6.5 allows an attacker to partially extract confidential configurations via user-space emulation.","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-2018-12337","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2018-12338"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2018-12336"},"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":8.1,"headline":"Security feature bypass in n/a","id":"CVE-2018-12333","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.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":"An attacker can partially extract confidential configurations from the ECOS Secure Boot Stick via user-space emulation, exposing sensitive settings.","url":"https://insights.sbomify.com/CVE-2018-12337/"}