Menu

Star on GitHub · 3.2k

CVE-2006-3912

2.1 · LOW

Stack-based buffer overflow in the SFX module in WinRAR before 3.60 beta 8 has unspecified vectors and impact.

Published Jul 28, 2006rarlabCWE-119EPSS 5.67%

Overview

CVE-2006-3912 is a low-severity vulnerability affecting rarlab winrar. It was published on July 28, 2006 and has a CVSS 2.0 base score of 2.1 (LOW).

This vulnerability has a CVSS 2.0 base score of 2.1, rated LOW. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

Stack-based buffer overflow in the SFX module in WinRAR before 3.60 beta 8 has unspecified vectors and impact.

Remediation

Check the references section for vendor advisories and patches from rarlab. Update winrar to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2006-3912?

CVE-2006-3912 is a low-severity vulnerability affecting rarlab winrar. It was published on July 28, 2006 and has a CVSS 2.0 base score of 2.1 (LOW).

How severe is CVE-2006-3912?

This vulnerability has a CVSS 2.0 base score of 2.1, rated LOW. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2006-3912?

Check the references section for vendor advisories and patches from rarlab. Update winrar to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2006-3912?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2006-3912 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2006

View all