{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2018-8857 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-8857 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-8857 is a high-severity vulnerability in Philips Brilliance CT Scanners, published on 4 May 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-8857 and fix it if it is affected.\n\nWhat it is: CVE-2018-8857 is a high-severity vulnerability in Philips Brilliance CT Scanners, published on 4 May 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-8857 in the wild and no public exploit code.\n\nAffected product: Philips Brilliance CT Scanners. 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-8857/ (Markdown: https://insights.sbomify.com/CVE-2018-8857/index.md)","id":"CVE-2018-8857","markdown":"https://insights.sbomify.com/CVE-2018-8857/index.md","name":"CVE-2018-8857","record":{"aliases":["GHSA-qwwm-8j3m-f3mj"],"analysis":{"component_type":"ics_ot","fix_type":"patch","impacts":["account_takeover","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Medical CT Scanner","requires_auth":"low_privilege","summary":"Attackers can use hardcoded credentials to gain unauthorized access to Philips Brilliance CT scanners, compromising system integrity and data.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"_brilliance_ct_big_bore_firmware","vendor":"philips"},{"product":"brilliance_firmware_64","vendor":"philips"},{"product":"brilliance_ict_firmware","vendor":"philips"},{"product":"brilliance_ict_sp_firmware","vendor":"philips"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"Philips Brilliance CT software (Brilliance 64 version 2.6.2 and prior, Brilliance iCT versions 4.1.6 and prior, Brillance iCT SP versions 3.2.4 and prior, and Brilliance CT Big Bore 2.3.5 and prior) contains fixed credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. An attacker could compromise these credentials and gain 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":"Hardcoded credentials in Brilliance CT Scanners","id":"CVE-2018-8857","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Hardcoded credentials in VGo Robot","id":"CVE-2018-8858"},"packages":[],"prev":{"headline":"Hardcoded credentials in e-Alert Unit (non-medical device)","id":"CVE-2018-8856"},"products":["Brilliance CT Scanners"],"published":"2018-05-04","related":[{"cvss_score":8.8,"headline":"Privilege escalation in Brilliance CT Scanners","id":"CVE-2018-8853","kev_date_added":null,"published":"2018-05-04"},{"cvss_score":8.7,"headline":"Privilege escalation in Brilliance CT Scanners","id":"CVE-2018-8861","kev_date_added":null,"published":"2018-05-04"}],"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-09-16","vendors":["Philips"]},"summary":"Attackers can use hardcoded credentials to gain unauthorized access to Philips Brilliance CT scanners, compromising system integrity and data.","url":"https://insights.sbomify.com/CVE-2018-8857/"}