CVE-2001-0153 Buffer overflow in VB-TSQL debugger object (vbsdicli.exe) in Visual Studio 6.0 Enterprise Edition allows remote attackers to execute arbitrary commands.
High 7.5
Published
Updated
Check this codebase for CVE-2001-0153 and fix it if it is affected.
What it is: CVE-2001-0153 is a high-severity vulnerability in Microsoft Visual Studio, published on 7 May 2001.
Exploitation: There is no known exploitation of CVE-2001-0153 in the wild and no public exploit code.
Affected product: Microsoft Visual Studio. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2001-0153/ (Markdown: https://insights.sbomify.com/CVE-2001-0153/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2001-0153?
CVE-2001-0153 is a high-severity vulnerability in Microsoft Visual Studio, published on 7 May 2001.
Official description
Buffer overflow in VB-TSQL debugger object (vbsdicli.exe) in Visual Studio 6.0 Enterprise Edition allows remote attackers to execute arbitrary commands.
Weakness: CWE-119
Which versions are affected by CVE-2001-0153?
It affects 2 products.
Products include Microsoft Visual Basic, Microsoft Visual Studio.
How do I fix CVE-2001-0153?
No fix has been published for CVE-2001-0153 yet. Limit exposure of the affected software until one is available.
Is CVE-2001-0153 being exploited?
There is no known exploitation of CVE-2001-0153 in the wild and no public exploit code.
Other vulnerabilities in Microsoft Visual Studio
Sources
Also known as GHSA-52wx-ppx5-cwp9.