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

CVE-2013-7104 has a CVSS 2.0 base score of 9.0 (Critical). CVSS vector: AV:N/AC:L/Au:S/C:C/I:C/A:C. EPSS exploitation probability: 0.7%.

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

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

Email Gateway CVE-2013-7104

CRITICAL

OS Command Injection (CWE-78)

2013-12-14 cve@mitre.org

Command Injection Email Gateway

9.0

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

9.0 CRITICAL

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

Dec 14, 2013 - 17:21 cve.org

CRITICAL 9.0

DescriptionCVE.org

McAfee Email Gateway 7.6 allows remote authenticated administrators to execute arbitrary commands by specifying them in the value attribute in a (1) Command or (2) Script XML element. NOTE: this issue can be combined with CVE-2013-7092 to allow remote attackers to execute commands.

AnalysisAI

McAfee Email Gateway 7.6 allows remote authenticated administrators to execute arbitrary commands by specifying them in the value attribute in a (1) Command or (2) Script XML element. Rated critical severity (CVSS 9.0), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified as OS Command Injection (CWE-78), which allows attackers to execute arbitrary operating system commands on the host. McAfee Email Gateway 7.6 allows remote authenticated administrators to execute arbitrary commands by specifying them in the value attribute in a (1) Command or (2) Script XML element. NOTE: this issue can be combined with CVE-2013-7092 to allow remote attackers to execute commands. Affected products include: Mcafee Email Gateway.

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.