{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1000627 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-1000627 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-1000627 is a critical vulnerability in n/a, published on 28 Dec 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-1000627 and fix it if it is affected.\n\nWhat it is: CVE-2018-1000627 is a critical vulnerability in n/a, published on 28 Dec 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-1000627 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-1000627/ (Markdown: https://insights.sbomify.com/CVE-2018-1000627/index.md)","id":"CVE-2018-1000627","markdown":"https://insights.sbomify.com/CVE-2018-1000627/index.md","name":"CVE-2018-1000627","record":{"aliases":["GHSA-h89g-92w5-6r7q"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"V2I Hub","requires_auth":"none","summary":"Remote attackers can access the API key file to obtain sensitive credentials and gain unauthorized system access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"v2i_hub","vendor":"battelle"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"Battelle V2I Hub 2.5.1 could allow a remote attacker to obtain sensitive information, caused by the failure to restrict access to the API key file. An attacker could exploit this vulnerability to obtain the current API key to gain unauthorized access to the system.","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-1000627","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":"Auth bypass in n/a","id":"CVE-2018-1000628"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2018-1000626"},"products":["n/a"],"published":"2018-12-28","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2018-1000625","kev_date_added":null,"published":"2018-12-28"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2018-1000626","kev_date_added":null,"published":"2018-12-28"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2018-1000628","kev_date_added":null,"published":"2018-12-28"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2018-1000631","kev_date_added":null,"published":"2018-12-28"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2018-1000624","kev_date_added":null,"published":"2018-12-28"},{"cvss_score":7.2,"headline":"SQL injection in n/a","id":"CVE-2018-1000630","kev_date_added":null,"published":"2018-12-28"}],"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":"Remote attackers can access the API key file to obtain sensitive credentials and gain unauthorized system access.","url":"https://insights.sbomify.com/CVE-2018-1000627/"}