CVE-2013-5016
First published: Thu May 08 2014(Updated: )
Symantec Critical System Protection (SCSP) before 5.2.9, when installed on an unpatched Windows Server 2003 R2 platform, allows remote attackers to bypass policy settings via unspecified vectors.
Credit: secure@symantec.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Broadcom Symantec Critical System Protection | <=5.2.8 | |
| Microsoft Windows Server 2003 | =r2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2013-5016?
CVE-2013-5016 is classified as a medium severity vulnerability.
How do I fix CVE-2013-5016?
To fix CVE-2013-5016, upgrade Symantec Critical System Protection to version 5.2.9 or higher.
What platforms are affected by CVE-2013-5016?
CVE-2013-5016 affects Symantec Critical System Protection installed on unpatched Windows Server 2003 R2.
Can CVE-2013-5016 be exploited remotely?
Yes, CVE-2013-5016 allows remote attackers to bypass policy settings.
What should I do if I am running an affected version of Symantec Critical System Protection?
If you are running an affected version, it is critical to upgrade to the patched version as soon as possible.
- agent/type
- agent/references
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/weakness
- agent/severity
- agent/last-modified-date
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/broadcom
- canonical/broadcom symantec critical system protection
- version/broadcom symantec critical system protection/5.2.8
- vendor/microsoft
- canonical/microsoft windows server 2003
- version/microsoft windows server 2003/r2