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

CVE-2013-4479 has a CVSS 2.0 base score of 6.8 (Medium). CVSS vector: AV:N/AC:M/Au:N/C:P/I:P/A:P. EPSS exploitation probability: 0.5%.

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

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

Is there a patch available for CVE-2013-4479?

Yes, a patch is available for CVE-2013-4479. Update the affected software to the latest version immediately.

Sup CVE-2013-4479

MEDIUM

Code Injection (CWE-94)

2013-12-07 secalert@redhat.com

Code Injection RCE Sup

6.8

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

6.8 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

Dec 07, 2013 - 20:55 cve.org

MEDIUM 6.8

DescriptionCVE.org

lib/sup/message_chunks.rb in Sup before 0.13.2.1 and 0.14.x before 0.14.1.1 allows remote attackers to execute arbitrary commands via shell metacharacters in the content_type of an email attachment.

AnalysisAI

lib/sup/message_chunks.rb in Sup before 0.13.2.1 and 0.14.x before 0.14.1.1 allows remote attackers to execute arbitrary commands via shell metacharacters in the content_type of an email attachment. Rated medium severity (CVSS 6.8), this vulnerability is remotely exploitable. Public exploit code available.

Technical ContextAI

This vulnerability is classified as Code Injection (CWE-94), which allows attackers to inject and execute arbitrary code within the application. lib/sup/message_chunks.rb in Sup before 0.13.2.1 and 0.14.x before 0.14.1.1 allows remote attackers to execute arbitrary commands via shell metacharacters in the content_type of an email attachment. Affected products include: Supmua Sup. Version information: before 0.13.2.1.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Never evaluate user-controlled input as code. Use sandboxing, disable dangerous functions, apply strict input validation.