Security readout for executives and security teams
Plain-English summary
This issue can let a local user crash a Windows system running 2345 Security Guard 3.6 by abusing its kernel driver. The known impact is denial of service through BSOD; the CVE also says other impact is possible but unspecified.
Executive priority
Treat this as a targeted endpoint stability risk, especially on shared or high-availability systems. Prioritize inventory and replacement decisions where the product is still present.
Technical view
CVE-2018-8894 affects 2345 Security Guard 3.6 driver 2345BdPcSafe.sys. The driver does not validate input values for IOCtl 0x00222108, allowing local users to trigger BSOD and possibly other unspecified impact. No CVSS, CWE, or vendor fix is provided in the bundle.
Likely exposure
Exposure appears limited to Windows endpoints with 2345 Security Guard 3.6 installed and 2345BdPcSafe.sys loaded. The cited CVE describes local-user access, not remote network exposure.
Exploitation context
A public GitHub reference exists for a BSOD proof of concept. The source bundle does not show confirmed active exploitation, and the CVE is not listed as KEV.
Researcher notes
The evidence supports local denial of service through improper IOCTL input validation. Claims beyond BSOD remain uncertain because the CVE says other impact is unspecified and no technical advisory or patch details are included.
Mitigation direction
- Identify systems running 2345 Security Guard 3.6.
- Check vendor guidance for a fixed or supported version.
- Remove or disable the affected product where it is not required.
- Limit local interactive access on systems that must keep the driver.
- Monitor for crashes involving 2345BdPcSafe.sys.
Validation and detection
- Inventory endpoints for 2345 Security Guard 3.6.
- Confirm whether 2345BdPcSafe.sys is present and loaded.
- Review crash dumps or event logs for 2345BdPcSafe.sys BSODs.
- Verify any installed replacement version against vendor guidance.
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-8894 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/D0neMkj/POC_BSOD/tree/master/2345%20security%20guard/0x00222108CVE 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.