Menu

Star on GitHub · 3.2k

CVE-2015-8801

2.9 · LOW

Race condition in the client in Symantec Endpoint Protection (SEP) 12.1 before RU6 MP5 allows local users to bypass intended restrictions on USB file transfer by conducting filesystem operations be…

Published Jun 30, 2016CWE-254EPSS 0.27%

Overview

CVE-2015-8801 is a low-severity vulnerability. It was published on June 30, 2016 and has a CVSS 3.0 base score of 2.9 (LOW).

This vulnerability has a CVSS 3.0 base score of 2.9, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

Race condition in the client in Symantec Endpoint Protection (SEP) 12.1 before RU6 MP5 allows local users to bypass intended restrictions on USB file transfer by conducting filesystem operations before the SEP device manager recognizes a new USB device.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2015-8801?

CVE-2015-8801 is a low-severity vulnerability. It was published on June 30, 2016 and has a CVSS 3.0 base score of 2.9 (LOW).

How severe is CVE-2015-8801?

This vulnerability has a CVSS 3.0 base score of 2.9, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2015-8801?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2015-8801?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2015-8801 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2015

View all