Prior to SEE v11.1.3MP1, Symantec Endpoint Encryption can be susceptible to a denial of…
Priority LOW 21Published · Updated
Key facts
- Attack vector
- Adjacent network
- Privileges required
- High
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- No fix listed
Attack profile from CVSS 3.0 · NVD. Fix status from CNA.
Summary
Prior to SEE v11.1.3MP1, Symantec Endpoint Encryption can be susceptible to a denial of service (DoS) attack, which is a type of attack whereby the perpetrator attempts to make a particular machine or network resource unavailable to its intended users by temporarily or indefinitely disrupting services of a specific host within a network.
Why it matters now
EPSS 0.00272 19th 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-2017-15525
- 2026-10-03 Alias added: GHSA-f4hx-m36j-86cj
References
More Symantec Endpoint Encryption vulnerabilities
- TI-2019-07093 Symantec Endpoint Encryption prior to SEE 11.2.1 MP1 may be susceptible to a Privilege… CVSS 3.0HIGH 7.8
- TI-2016-05641 Improper privilege management in Symantec IT Management Suite CVSS 3.1HIGH 7.8
- TI-2015-06763 Unquoted Windows search path vulnerability in EEDService in Symantec Endpoint Encryption… CVSS 3.0HIGH 7.8
- TI-2019-07102 Symantec Endpoint Encryption, prior to SEE 11.3.0, may be susceptible to a privilege… CVSS 3.0HIGH 7.8
- TI-2019-07101 Symantec Endpoint Encryption, prior to SEE 11.3.0, may be susceptible to a privilege… CVSS 3.0HIGH 7.8
- TI-2017-11348 NULL pointer dereference in Symantec Endpoint Encryption CVSS 3.0MEDIUM 6.8
Sources
- CVE-2017-15525 · CVE Program
- CVE-2017-15525 · NVD
- FIRST EPSS
- GHSA-f4hx-m36j-86cj · 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