Security readout for executives and security teams
Plain-English summary
This is a local Windows driver issue in 2345 Security Guard 3.7. A user already on the machine could crash the system with a blue screen. The source also says other impact may be possible, but does not define it.
Executive priority
Treat this as an operational stability risk rather than a confirmed remote breach path. Prioritize remediation where the software runs on critical endpoints, shared workstations, or systems requiring high availability.
Technical view
CVE-2018-10955 describes missing input validation in the x64 2345BdPcSafe.sys driver. The reported attack path is local access to the driver interface through IOCTL 0x00222548, causing denial of service and possibly unspecified additional impact.
Likely exposure
Exposure appears limited to Windows systems running 2345 Security Guard 3.7 with the x64 2345BdPcSafe.sys driver installed. The source bundle does not provide CPEs, vendor advisory details, or fixed versions.
Exploitation context
The CVE is not listed in KEV in the provided bundle. A public GitHub PoC reference exists, but the sources do not show confirmed active exploitation in the wild.
Researcher notes
Evidence is sparse: no CVSS, CWE, CPE, patch statement, or vendor advisory is included. The GitHub reference indicates public disclosure of a PoC, but validation should focus on presence and version, not exploit reproduction.
Mitigation direction
- Inventory endpoints for 2345 Security Guard 3.7 and 2345BdPcSafe.sys.
- Check vendor guidance for fixed versions or removal recommendations.
- Remove the affected product where it is unnecessary or unsupported.
- Limit local interactive access on exposed workstations and shared systems.
- Prioritize systems where crashes affect operations or security monitoring.
Validation and detection
- Confirm whether 2345BdPcSafe.sys x64 is present on Windows endpoints.
- Identify installed 2345 Security Guard versions, especially 3.7.
- Review endpoint crash history for unexplained BSOD events.
- Check whether the driver is loaded on business-critical systems.
- Record compensating controls for systems that cannot be changed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2018-10955 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/anhkgg/poc/tree/master/2345%20security%20guard/2345BdPcSafe.sys-x64-0x00222548CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.