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

CVE-2013-1616 has a CVSS 2.0 base score of 8.3 (High). CVSS vector: AV:A/AC:L/Au:N/C:C/I:C/A:C. EPSS exploitation probability: 15.7%.

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

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

Web Gateway CVE-2013-1616

HIGH

OS Command Injection (CWE-78)

2013-08-01 secure@symantec.com

Command Injection Web Gateway Web Gateway Appliance 8450 Web Gateway Appliance 8490

8.3

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

8.3 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Adjacent

Attack Complexity

Low

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

Aug 01, 2013 - 13:32 cve.org

HIGH 8.3

DescriptionCVE.org

The management console on the Symantec Web Gateway (SWG) appliance before 5.1.1 allows remote attackers to execute arbitrary commands by injecting a command into an application script.

AnalysisAI

The management console on the Symantec Web Gateway (SWG) appliance before 5.1.1 allows remote attackers to execute arbitrary commands by injecting a command into an application script. Rated high severity (CVSS 8.3), this vulnerability is low attack complexity. Public exploit code available and EPSS exploitation probability 15.7%.

Technical ContextAI

This vulnerability is classified as OS Command Injection (CWE-78), which allows attackers to execute arbitrary operating system commands on the host. The management console on the Symantec Web Gateway (SWG) appliance before 5.1.1 allows remote attackers to execute arbitrary commands by injecting a command into an application script. Affected products include: Symantec Web Gateway, Symantec Web Gateway Appliance 8450, Symantec Web Gateway Appliance 8490. Version information: before 5.1.1.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Avoid passing user input to shell commands. Use language-specific APIs instead of shell execution. Apply strict input validation with allowlists.