Stack-based buffer overflow in Broadcom products - CVE-2016-2209
Published: June 30, 2016 / Updated: July 12, 2020
Vulnerability identifier: #VU62
CSH Severity: High
CVSS v4: 8.8 [CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N]
CVE-ID: CVE-2016-2209
CWE-ID: CWE-319
Exploitation vector: Remote access
Exploit availability:
Public exploit is available
Vulnerability details
The vulnerability allows a remote attacker to execute arbitrary code on the target system.
The vulnerability exists due to boundary error when parsing a maliciously-formed PowerPoint PPT file. A remote unauthenticated attacker can cause stacked-based buffer overflow by sending a specially crafted file to vulnerable server.
Successful exploitation of this vulnerability may result in in arbitrary code execution.
The vulnerability exists due to boundary error when parsing a maliciously-formed PowerPoint PPT file. A remote unauthenticated attacker can cause stacked-based buffer overflow by sending a specially crafted file to vulnerable server.
Successful exploitation of this vulnerability may result in in arbitrary code execution.
Affected software
Symantec Data Center Security:Server (SDCS:S)
Symantec Protection for SharePoint Servers (SPSS)
Symantec Mail Security for Microsoft Exchange (SMSMSE)
Symantec Mail Security for Domino (SMSDOM)
Symantec Protection Engine (SPE)
Symantec Scan Engine
Symantec Endpoint Protection
Symantec Protection for SharePoint Servers (SPSS)
Symantec Mail Security for Microsoft Exchange (SMSMSE)
Symantec Mail Security for Domino (SMSDOM)
Symantec Protection Engine (SPE)
Symantec Scan Engine
Symantec Endpoint Protection
How to mitigate CVE-2016-2209
Updates to resolve these issues can be installed using product update functionality. Users of Symantec Endpoint Protection (SEP), Symantec Protection Engine (SPE), Symantec Protection for SharePoint Servers (SPSS), Symantec Mail Security for Microsoft Exchange (SMSMSE) and Symantec Mail Security for Domino (SMSDOM) should apply custom patches. For more information, please refer to vendors advisory, specified in External links section.