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

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

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

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

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

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

Rgpg CVE-2013-4203

HIGH

Code Injection (CWE-94)

2013-10-11 secalert@redhat.com

Code Injection RCE Rgpg

7.5

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

Oct 11, 2013 - 22:55 cve.org

HIGH 7.5

DescriptionCVE.org

The self.run_gpg function in lib/rgpg/gpg_helper.rb in the rgpg gem before 0.2.3 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in unspecified vectors.

AnalysisAI

The self.run_gpg function in lib/rgpg/gpg_helper.rb in the rgpg gem before 0.2.3 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in unspecified vectors. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, low attack complexity. 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. The self.run_gpg function in lib/rgpg/gpg_helper.rb in the rgpg gem before 0.2.3 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in unspecified vectors. Affected products include: Richard Cook Rgpg. Version information: before 0.2.3.

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.