CVE Tools

CVE-2006-3649

Exploitation likely. EPSS gives it a 10% chance of exploitation in the next 30 days. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

What it is

From the CVE record

Buffer overflow in Microsoft Visual Basic for Applications (VBA) SDK 6.0 through 6.4, as used by Microsoft Office 2000 SP3, Office XP SP3, Project 2000 SR1, Project 2002 SP1, Access 2000 Runtime SP3, Visio 2002 SP2, and Works Suite 2004 through 2006, allows user-assisted attackers to execute arbitrary code via unspecified document properties that are not verified when VBA is invoked to open documents.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS96th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

10% chance of exploitation activity in the next 30 days, which ranks it in the 96th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

5 events over 7215 days, from the signal feeds we watch.

  1. EPSS band changehigh → moderate
  2. Patch availablerecord updated
  3. Publishedweakness classified

Affected products

And 1 more affected product. See all after sign-in

Technical detail

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

Scored 5.1 by NVD.

How it is reached

  • Access Vector NetworkExploitable remotely over the network
  • Access Complexity HighSpecialized conditions required
  • Authentication NoneNo authentication required

Impact if exploited

  • Confidentiality PartialSome information is disclosed
  • Integrity PartialSome data can be modified
  • Availability PartialReduced performance or service disruption

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Visual Basic, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store