What is the CVSS score of CVE-2013-1612?

CVE-2013-1612 has a CVSS 2.0 base score of 7.9 (High). CVSS vector: AV:A/AC:M/Au:N/C:C/I:C/A:C. EPSS exploitation probability: 2.7%.

Is there a public PoC exploit available for CVE-2013-1612?

Yes, a public proof-of-concept exploit is available for CVE-2013-1612. Prioritise patching immediately. EPSS: 2.7%.

Endpoint Protection Manager CVE-2013-1612

HIGH

Buffer Overflow (CWE-119)

2013-06-20 secure@symantec.com

Buffer Overflow RCE Endpoint Protection Manager Endpoint Protection Center

7.9

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

7.9 HIGH

AV:A/AC:M/Au:N/C:C/I:C/A:C

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:A/AC:M/Au:N/C:C/I:C/A:C

Attack Vector

Adjacent

Attack Complexity

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

Jun 20, 2013 - 03:17 cve.org

HIGH 7.9

DescriptionCVE.org

Buffer overflow in secars.dll in the management console in Symantec Endpoint Protection Manager (SEPM) 12.1.x before 12.1.3, and Symantec Endpoint Protection Center (SPC) Small Business Edition 12.0.x, allows remote attackers to execute arbitrary code via unspecified vectors.

AnalysisAI

Buffer overflow in secars.dll in the management console in Symantec Endpoint Protection Manager (SEPM) 12.1.x before 12.1.3, and Symantec Endpoint Protection Center (SPC) Small Business Edition. Rated high severity (CVSS 7.9). Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified as Buffer Overflow (CWE-119), which allows attackers to corrupt memory to execute arbitrary code or crash the application. Buffer overflow in secars.dll in the management console in Symantec Endpoint Protection Manager (SEPM) 12.1.x before 12.1.3, and Symantec Endpoint Protection Center (SPC) Small Business Edition 12.0.x, allows remote attackers to execute arbitrary code via unspecified vectors. Affected products include: Symantec Endpoint Protection Manager, Symantec Endpoint Protection Center. Version information: before 12.1.3.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Use memory-safe languages or bounds-checking. Enable ASLR, DEP/NX, stack canaries. Use safe string functions.