Symantec Critical System Protection (SCSP) before 5.2.9, when installed on an unpatched Windows Server 2003 R2 platform, allows remote atta…

published 2014-05-08 12y ago modified 2026-06-16 4mo ago also EUVD-2013-4858

cvss: 7.6; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 2.4%; EPSS 2.4% chance of exploitation in 30 days, percentile 83%
public exploits: 0; none known

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.

Is CVE-2013-5016 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

2.35% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	2.0	7.6	AV:N/AC:H/Au:N/C:C/I:C/A:C

Classification

Weakness

CWE-264 Permissions, Privileges, and Access Controls

References

symantec.com /security_response/securityupdates/detail.jsp?fid=security_advisory&pvid=security_advisory&year=&suid=20140502
vendor-advisory
securityfocus.com /bid/67161
vdb-entry

Sources

CVE List CVE-2013-5016
NVD CVE-2013-5016

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.