What is the CVSS score of CVE-2012-1795?

CVE-2012-1795 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.1%.

Is there a public PoC exploit available for CVE-2012-1795?

Yes, a public proof-of-concept exploit is available for CVE-2012-1795. Prioritise patching immediately. EPSS: 1.1%.

Is there a patch available for CVE-2012-1795?

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

Webglimpse CVE-2012-1795

HIGH

OS Command Injection (CWE-78)

2012-03-20 cve@mitre.org

Command Injection Webglimpse

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

Mar 20, 2012 - 18:55 cve.org

HIGH 7.5

DescriptionCVE.org

webglimpse.cgi in Webglimpse before 2.20.0 allows remote attackers to execute arbitrary commands via shell metacharacters in the query parameter, as exploited in the wild in March 2012.

AnalysisAI

webglimpse.cgi in Webglimpse before 2.20.0 allows remote attackers to execute arbitrary commands via shell metacharacters in the query parameter, as exploited in the wild in March 2012. 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 OS Command Injection (CWE-78), which allows attackers to execute arbitrary operating system commands on the host. webglimpse.cgi in Webglimpse before 2.20.0 allows remote attackers to execute arbitrary commands via shell metacharacters in the query parameter, as exploited in the wild in March 2012. Affected products include: Webglimpse. Version information: before 2.20.0.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Avoid passing user input to shell commands. Use language-specific APIs instead of shell execution. Apply strict input validation with allowlists.