Visual Basic vulnerabilitiesAnd the versions its exploited flaws hit.
Visual Basic is made by Microsoft. We track 19 published vulnerabilities listed under that exact name, across 7 versions. 2 of them are on the list of flaws known to be exploited, the newest added on 3 March 2022. Microsoft lists newer releases under their own names, such as Visual Basic for Applications, so check those pages too.
The most recent Visual Basic flaw added to the known-exploited list is CVE-2012-1856, on 3 March 2022. We keep watching the known-exploited list.
Is Visual Basic listed under other names? Yes.
Microsoft also lists Visual Basic under more specific names, such as Visual Basic for Applications and Visual Basic Enterprise Edition. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which versions of Visual Basic do the exploited flaws hit?
Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.
- CVE-2012-1856Exploited list, 3 Mar 2022
Microsoft Office MSCOMCTL.OCX Remote Code Execution Vulnerability
6.0 - CVE-2012-0158Exploited list, 3 Nov 2021
Microsoft MSCOMCTL.OCX Remote Code Execution Vulnerability
6.0
Which Visual Basic vulnerabilities are being exploited?
2 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 8.8Microsoft Office MSCOMCTL.OCX Remote Code Execution Vulnerability
The TabStrip ActiveX control in the Common Controls in MSCOMCTL.OCX in Microsoft Office allows remote attackers to execute arbitrary code via a crafted (1) document or (2) web page that triggers system-state corruption.
- 8.8Microsoft MSCOMCTL.OCX Remote Code Execution Vulnerability
Microsoft MSCOMCTL.OCX contains an unspecified vulnerability that allows for remote code execution, allowing an attacker to take complete control of an affected system under the context of the current user.
Which Visual Basic flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 55%CVE-2003-0347Critical
Heap-based buffer overflow in VBE.DLL and VBE6.DLL of Microsoft Visual Basic for Applications (VBA) SDK 5.0 through 6.3 allows remote attackers to execute arbitrary code via a document with a long ID parameter.
- 49%CVE-2004-0200Critical
Buffer overflow in the JPEG (JPG) parsing engine in the Microsoft Graphic Device Interface Plus (GDI+) component, GDIPlus.dll, allows remote attackers to execute arbitrary code via a JPEG image with a small JPEG COM...
- 49%CVE-2007-4776Critical
Buffer overflow in Microsoft Visual Basic 6.0 and Enterprise Edition 6.0 SP6 allows user-assisted remote attackers to execute arbitrary code via a Visual Basic project (vbp) file containing a long Reference line,...
- 36%CVE-2007-2884Critical
Multiple stack-based buffer overflows in Microsoft Visual Basic 6 allow user-assisted remote attackers to cause a denial of service (CPU consumption) or execute arbitrary code via a Visual Basic Project (vbp) file...
Running Visual Basic? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
The TabStrip ActiveX control in the Common Controls in MSCOMCTL.OCX in Microsoft Office allows remote attackers to execute arbitrary code via a crafted (1) document or (2) web page that triggers system-state corruption.
- Matched to
- Visual Basic on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 19 published vulnerabilities listed under the name Visual Basic, across 7 versions. The most recent Visual Basic flaw added to the known-exploited list is CVE-2012-1856, on 3 March 2022.
2 are on the list of flaws known to be exploited. The most recently added are CVE-2012-1856 and CVE-2012-0158.
Microsoft also lists Visual Basic under more specific names, such as Visual Basic for Applications and Visual Basic Enterprise Edition. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Each flaw names its own versions, usually as ranges. The newest, CVE-2012-1856, affects 6.0. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Visual Basic. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.