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

CVE-2012-3386 has a CVSS 2.0 base score of 4.4 (Medium). CVSS vector: AV:L/AC:M/Au:N/C:P/I:P/A:P. EPSS exploitation probability: 0.2%.

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

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

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

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

Automake CVE-2012-3386

MEDIUM

Permissions, Privileges, and Access Controls (CWE-264)

2012-08-07 secalert@redhat.com

Privilege Escalation RCE Automake

4.4

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

4.4 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Local

Attack Complexity

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

Aug 07, 2012 - 21:55 cve.org

MEDIUM 4.4

DescriptionCVE.org

The "make distcheck" rule in GNU Automake before 1.11.6 and 1.12.x before 1.12.2 grants world-writable permissions to the extraction directory, which introduces a race condition that allows local users to execute arbitrary code via unspecified vectors.

AnalysisAI

The "make distcheck" rule in GNU Automake before 1.11.6 and 1.12.x before 1.12.2 grants world-writable permissions to the extraction directory, which introduces a race condition that allows local. Rated medium severity (CVSS 4.4). Public exploit code available.

Technical ContextAI

This vulnerability is classified under CWE-264. The "make distcheck" rule in GNU Automake before 1.11.6 and 1.12.x before 1.12.2 grants world-writable permissions to the extraction directory, which introduces a race condition that allows local users to execute arbitrary code via unspecified vectors. Affected products include: Gnu Automake. Version information: before 1.11.6.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.