Access control flaw in Intel Data Loss Prevention Endpoint
Priority LOW 34CWE-264Published · Updated
Key facts
- Attack vector
- Local
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- No fix listed
Attack profile from CVSS 3.0 · NVD. Fix status from CNA. Impact type from CWE-264.
Summary
Access control vulnerability in Intel Security Data Loss Prevention Endpoint (DLPe) 9.4.200 and 9.3.600 allows authenticated users with Read-Write-Execute permissions to inject hook DLLs into other processes via pages in the target process memory get.
Why it matters now
EPSS 0.00311 24th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2016-8012
- 2026-10-03 Alias added: GHSA-8p8m-62w6-3xj8
References
More Intel vulnerabilities
- TI-2021-19919 Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints KEVCVSS 3.1CRITICAL 10.0
- TI-2017-03684 Improper privilege management in Intel Active Mangement Technology, Intel Small Business… KEVCVSS 3.1CRITICAL 9.8
- TI-2021-20393 Apache Log4j2 Thread Context Message Pattern and Context Lookup Pattern vulnerable to a denial of service attack KEVCVSS 3.1CRITICAL 9.0
- TI-2015-02024 (1) IQVW32.sys before 1.3.1.0 and (2) IQVW64.sys before 1.3.1.0 in the Intel Ethernet… KEVCVSS 3.1HIGH 7.8
- TI-2013-04197 The IPMI 2.0 specification supports RMCP+ Authenticated Key-Exchange Protocol (RAKP)… CVSS 3.0HIGH 7.5
- TI-2022-07265 An issue was discovered in the DNS proxy in Connman through 1.40. CVSS 3.1CRITICAL 9.1
Sources
- CVE-2016-8012 · CVE Program
- CVE-2016-8012 · NVD
- FIRST EPSS
- GHSA-8p8m-62w6-3xj8 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences