Microsoft Visual Studio 6.0 VB-TSQL Debugger vbsdicli.exe memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in Microsoft Visual Studio 6.0. This vulnerability affects unknown code of the file vbsdicli.exe of the component VB-TSQL Debugger. The manipulation results in memory corruption. This vulnerability is reported as CVE-2001-0153. No exploit exists. A patch should be applied to remediate this issue.
Details
A vulnerability was found in Microsoft Visual Studio 6.0 (Programming Tool Software). It has been classified as critical. Affected is an unknown code block of the file vbsdicli.exe of the component VB-TSQL Debugger. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
Buffer overflow in VB-TSQL debugger object (vbsdicli.exe) in Visual Studio 6.0 Enterprise Edition allows remote attackers to execute arbitrary commands.
The weakness was disclosed 05/03/2001 by BindView with Microsoft as MS01-018 as confirmed bulletin (Technet). The advisory is available at microsoft.com. This vulnerability is traded as CVE-2001-0153. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit.
Applying the patch MS01-018 is able to eliminate this problem. The bugfix is ready for download at microsoft.com.
The vulnerability is also documented in the databases at X-Force (6288), SecurityFocus (BID 2521†) and Vulnerability Center (SBV-4178†). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: MS01-018
Timeline
03/27/2001 🔍03/27/2001 🔍
05/03/2001 🔍
05/03/2001 🔍
04/19/2004 🔍
07/03/2014 🔍
05/21/2019 🔍
Sources
Vendor: microsoft.comAdvisory: MS01-018
Researcher: BindView
Organization: Microsoft
Status: Confirmed
CVE: CVE-2001-0153 (🔍)
GCVE (CVE): GCVE-0-2001-0153
GCVE (VulDB): GCVE-100-16602
X-Force: 6288
SecurityFocus: 2521 - Microsoft Visual Basic / Visual Studio 'VB T-SQL ' Buffer Overflow Vulnerability
Vulnerability Center: 4178 - [MS01-018] Buffer Overflow in Microsoft Visual Basic/Visual Studio VB-TSQL Object Enables Code Execu, High
Entry
Created: 07/03/2014 17:03Updated: 05/21/2019 09:54
Changes: 07/03/2014 17:03 (61), 05/21/2019 09:54 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.