The Execute method in the ADODB.Connection 2.7 and 2.8 ActiveX control objects (ADODB.Connection.2.7 and…
No fixed version listed yet.Check the vendor advisory. References ↓
The Execute method in the ADODB.Connection 2.7 and 2.8 ActiveX control objects, part of Microsoft Data Access Components (MDAC) 2.5 SP3, 2.7 SP1, 2.8, and 2.8 SP1, fails to properly track freed memory when the second argument is a BSTR. An attacker who can get a user to load a page with crafted strings in the second and third arguments can crash Internet Explorer and possibly execute arbitrary code.
Official description · CVE.org
The Execute method in the ADODB.Connection 2.7 and 2.8 ActiveX control objects (ADODB.Connection.2.7 and ADODB.Connection.2.8) in the Microsoft Data Access Components (MDAC) 2.5 SP3, 2.7 SP1, 2.8, and 2.8 SP1 does not properly track freed memory when the second argument is a BSTR, which allows remote attackers to cause a denial of service (Internet Explorer crash) and possibly execute arbitrary code via certain strings in the second and third arguments.
- Exploited
- Yes, in VulnCheck KEV
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 4 years after disclosure. Public exploit code (Exploit-DB) was available 3 days before disclosure.
- Public exploit codeExploit-DB3 days before
- Disclosedday 0
- First seen exploitedVulnCheck KEV evidence+4 yrs
What security researchers reported
Not named in any threat report yetAlso mentioned in 1 community threat pulse (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.