CVE-2016-9093 [High] | Input Validation Bypass in Endpoint Protection

A version of the SymEvent Driver that shipped with Symantec Endpoint Protection 12.1 RU6 MP6 and earlier fails to properly sanitize logged-in user input. SEP 14.0 and later are not impacted by this issue. A non-admin user would need to be able to save an executable file to disk and then be able to successfully run that file. If properly constructed, the file could access the driver interface and potentially manipulate certain system calls. On all 32-bit systems and in most cases on 64-bit systems, this will result in a denial of service that will crash the system. In very narrow circumstances, and on 64-bit systems only, this could allow the user to run arbitrary code on the local machine with kernel-level privileges. This could result in a non-privileged user gaining privileged access on the local machine.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.10%	0.40%	+0.29%
2	2025-03-30	0.21%	0.10%	-0.10%
3	2025-03-29	—	0.21%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.10%

0.40%

+0.29%

2025-03-30

0.21%

0.10%

-0.10%

2025-03-29

—

0.21%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.0	3.0	HIGH	`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.0	5.9	[email protected]
6.9	2.0	MEDIUM	`AV:L/AC:M/Au:N/C:C/I:C/A:C` Click to expand Access vector (AV:L) Requires local access to the target system. Access complexity (AC:M) Exploitation needs some favorable conditions, but not exceptional ones. Authentication (AU:N) No authentication is required. Confidentiality impact (C:C) Complete confidentiality impact. Integrity impact (I:C) Complete integrity impact. Availability impact (A:C) Complete availability impact.	3.4	10.0	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.0

3.0

HIGH

CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.0

5.9

[email protected]

6.9

2.0

MEDIUM

AV:L/AC:M/Au:N/C:C/I:C/A:C Click to expand

Access vector (AV:L): Requires local access to the target system.
Access complexity (AC:M): Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:C): Complete confidentiality impact.
Integrity impact (I:C): Complete integrity impact.
Availability impact (A:C): Complete availability impact.

3.4

10.0

[email protected]

Affected software / configurations for CVE-2016-9093

Vendor	Product	Version	Raw CPE
symantec	endpoint_protection	<= 12.1.6	cpe:2.3:a:symantec:endpoint_protection::::::::
symantec	endpoint_protection	12.1.6	cpe:2.3:a:symantec:endpoint_protection:12.1.6:mp1::::::
symantec	endpoint_protection	12.1.6	cpe:2.3:a:symantec:endpoint_protection:12.1.6:mp1a::::::
symantec	endpoint_protection	12.1.6	cpe:2.3:a:symantec:endpoint_protection:12.1.6:mp2::::::
symantec	endpoint_protection	12.1.6	cpe:2.3:a:symantec:endpoint_protection:12.1.6:mp3::::::
symantec	endpoint_protection	12.1.6	cpe:2.3:a:symantec:endpoint_protection:12.1.6:mp4::::::
symantec	endpoint_protection	12.1.6	cpe:2.3:a:symantec:endpoint_protection:12.1.6:mp5::::::
symantec	endpoint_protection	12.1.6	cpe:2.3:a:symantec:endpoint_protection:12.1.6:mp6::::::

References for CVE-2016-9093

URL	Tags
http://www.securityfocus.com/bid/96294	Third Party Advisory VDB Entry
http://www.securitytracker.com/id/1037961	Third Party Advisory VDB Entry
https://www.symantec.com/security_response/securityupdates/detail.jsp?fid=security_advisory&pvid=security_advisory&year=&suid=20170306_00	Vendor Advisory

URL

CVE-2016-9093

Exploit prediction scoring system (EPSS) score for CVE-2016-9093

Common vulnerability scoring system (CVSS) metrics for CVE-2016-9093

Weakness enumeration for CVE-2016-9093

Affected software / configurations for CVE-2016-9093

References for CVE-2016-9093