CVE-2016-2209: Buffer Overflow
Buffer overflow in Dec2SS.dll 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 execute arbitrary code via a crafted file.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2016-2209?
CVE-2016-2209 is classified as a high severity vulnerability due to the buffer overflow issue that may allow remote code execution.
How do I fix CVE-2016-2209?
To mitigate CVE-2016-2209, upgrade to the latest version of the affected Symantec products, ensuring that the updates address the vulnerability.
Which versions are affected by CVE-2016-2209?
CVE-2016-2209 affects several versions of Symantec products, including Symantec Advanced Threat Protection and Symantec Endpoint Protection prior to version 12.1 RU6 MP5.
What type of vulnerability is CVE-2016-2209?
CVE-2016-2209 is a buffer overflow vulnerability found in the Dec2SS.dll component of certain Symantec security products.
Is there a workaround for CVE-2016-2209?
While the best solution is to upgrade to the patched versions, temporarily disabling the affected component may reduce risk until an update is applied.