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

CVE-2012-3006 has a CVSS 2.0 base score of 7.1 (High). CVSS vector: AV:N/AC:H/Au:S/C:C/I:C/A:C. EPSS exploitation probability: 0.5%.

Mguard Firmware CVE-2012-3006

HIGH

Cryptographic Issues (CWE-310)

2012-06-19 ics-cert@hq.dhs.gov

Information Disclosure Mguard Firmware

7.1

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

7.1 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

High

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

Jun 19, 2012 - 18:55 cve.org

HIGH 7.1

DescriptionCVE.org

The Innominate mGuard Smart HW before HW-101130 and BD before BD-101030, mGuard industrial RS, mGuard delta HW before HW-103060 and BD before BD-211010, mGuard PCI, mGuard blade, and EAGLE mGuard appliances with software before 7.5.0 do not use a sufficient source of entropy for private keys, which makes it easier for man-in-the-middle attackers to spoof (1) HTTPS or (2) SSH servers by predicting a key value.

AnalysisAI

The Innominate mGuard Smart HW before HW-101130 and BD before BD-101030, mGuard industrial RS, mGuard delta HW before HW-103060 and BD before BD-211010, mGuard PCI, mGuard blade, and EAGLE mGuard. Rated high severity (CVSS 7.1), this vulnerability is remotely exploitable. No vendor patch available.

Technical ContextAI

This vulnerability is classified under CWE-310. The Innominate mGuard Smart HW before HW-101130 and BD before BD-101030, mGuard industrial RS, mGuard delta HW before HW-103060 and BD before BD-211010, mGuard PCI, mGuard blade, and EAGLE mGuard appliances with software before 7.5.0 do not use a sufficient source of entropy for private keys, which makes it easier for man-in-the-middle attackers to spoof (1) HTTPS or (2) SSH servers by predicting a key value. Affected products include: Innominate Mguard Firmware. Version information: before 7.5.0.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.