ghsa-qwwm-8j3m-f3mj
Vulnerability from github
Published
2022-05-13 01:31
Modified
2022-05-13 01:31
Severity ?
VLAI Severity ?
Details
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.
{ "affected": [], "aliases": [ "CVE-2018-8857" ], "database_specific": { "cwe_ids": [ "CWE-798" ], "github_reviewed": false, "github_reviewed_at": null, "nvd_published_at": "2018-05-04T17:29:00Z", "severity": "HIGH" }, "details": "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.", "id": "GHSA-qwwm-8j3m-f3mj", "modified": "2022-05-13T01:31:45Z", "published": "2022-05-13T01:31:45Z", "references": [ { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2018-8857" }, { "type": "WEB", "url": "https://ics-cert.us-cert.gov/advisories/ICSMA-18-123-01" }, { "type": "WEB", "url": "https://www.usa.philips.com/healthcare/about/customer-support/product-security" }, { "type": "WEB", "url": "http://www.securityfocus.com/bid/104088" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ] }
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…