CVE-2016-3645: Integer Overflow
Integer overflow in the TNEF unpacker in the AntiVirus Decomposer engine in Symantec Advanced Threat Protection (ATP); Symantec Data Center Security:Server (SDCS:S) 6.x through 6.6 MP1; Symantec Web Gateway; Symantec Endpoint Protection (SEP) before 12.1 RU6 MP5; Symantec Endpoint Protection (SEP) for Mac; Symantec Endpoint Protection (SEP) for Linux before 12.1 RU6 MP5; Symantec Protection Engine (SPE) before 7.0.5 HF01, 7.5.x before 7.5.3 HF03, 7.5.4 before HF01, and 7.8.0 before HF01; Symantec Protection for SharePoint Servers (SPSS) 6.0.3 through 6.0.5 before 6.0.5 HF 1.5 and 6.0.6 before HF 1.6; Symantec Mail Security for Microsoft Exchange (SMSMSE) before 7.03966002 HF1.1 and 7.5.x before 7.53966008 VHF1.2; Symantec Mail Security for Domino (SMSDOM) before 8.0.9 HF1.1 and 8.1.x before 8.1.3 HF1.2; CSAPI before 10.0.4 HF01; Symantec Message Gateway (SMG) before 10.6.1-4; Symantec Message Gateway for Service Providers (SMG-SP) 10.5 before patch 254 and 10.6 before patch 253; Norton AntiVirus, Norton Security, Norton Internet Security, and Norton 360 before NGC 22.7; Norton Security for Mac before 13.0.2; Norton Power Eraser (NPE) before 5.1; and Norton Bootable Removal Tool (NBRT) before 2016.1 allows remote attackers to have an unspecified impact via crafted TNEF data.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2016-3645?
CVE-2016-3645 is classified as a high-severity vulnerability due to its potential impact on affected Symantec products.
How does CVE-2016-3645 affect Symantec software?
CVE-2016-3645 affects the TNEF unpacker in multiple Symantec products, leading to potential integer overflow issues.
How do I fix CVE-2016-3645?
To mitigate CVE-2016-3645, users should upgrade to the latest versions of the affected Symantec products that have patched this vulnerability.
Which Symantec products are affected by CVE-2016-3645?
CVE-2016-3645 impacts various versions of Symantec Advanced Threat Protection, Symantec Endpoint Protection, and Symantec Data Center Security:Server, among others.
Is there a workaround for CVE-2016-3645?
No specific workarounds have been published for CVE-2016-3645; updating to patched versions is the recommended action.