What is the severity of CVE-2007-4891?

CVE-2007-4891 is rated as critical due to its ability to allow remote attackers to execute arbitrary programs on the affected system.

How do I fix CVE-2007-4891?

To mitigate CVE-2007-4891, users should upgrade to a patched version of Microsoft Visual Studio that addresses this vulnerability.

What platforms are affected by CVE-2007-4891?

CVE-2007-4891 affects Microsoft Visual Studio versions 6.0 and 6.0.0.9782.

What are the potential impacts of CVE-2007-4891?

Exploitation of CVE-2007-4891 could lead to unauthorized program execution and potential compromise of sensitive data.

Is CVE-2007-4891 still a risk today?

Although CVE-2007-4891 was disclosed in 2007, systems running the affected versions of Visual Studio remain vulnerable if they have not been updated.

Vulnerability/
CVE-2007-4891

medium

6.8

CWE

14/9/2007

7/8/2024

CVE-2007-4891: OS Command Injection

First published: Fri Sep 14 2007(Updated: )

A certain ActiveX control in PDWizard.ocx 6.0.0.9782 and earlier in Microsoft Visual Studio 6.0 exposes dangerous (1) StartProcess, (2) SyncShell, (3) SaveAs, (4) CABDefaultURL, (5) CABFileName, and (6) CABRunFile methods, which allows remote attackers to execute arbitrary programs and have other impacts, as demonstrated using absolute pathnames in arguments to StartProcess and SyncShell.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Microsoft Visual Studio	=6.0
Microsoft Visual Studio	=6.0.0.9782

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2007-4891?
CVE-2007-4891 is rated as critical due to its ability to allow remote attackers to execute arbitrary programs on the affected system.
How do I fix CVE-2007-4891?
To mitigate CVE-2007-4891, users should upgrade to a patched version of Microsoft Visual Studio that addresses this vulnerability.
What platforms are affected by CVE-2007-4891?
CVE-2007-4891 affects Microsoft Visual Studio versions 6.0 and 6.0.0.9782.
What are the potential impacts of CVE-2007-4891?
Exploitation of CVE-2007-4891 could lead to unauthorized program execution and potential compromise of sensitive data.
Is CVE-2007-4891 still a risk today?
Although CVE-2007-4891 was disclosed in 2007, systems running the affected versions of Visual Studio remain vulnerable if they have not been updated.

collector/nvd-historical
collector/nvd-index
agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/weakness
agent/severity
agent/last-modified-date
agent/author
agent/tags
agent/event
agent/description
agent/first-publish-date
agent/source
vendor/microsoft
canonical/microsoft visual studio
version/microsoft visual studio/6.0
version/microsoft visual studio/6.0.0.9782

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2007-4891?
CVE-2007-4891 is rated as critical due to its ability to allow remote attackers to execute arbitrary programs on the affected system.
How do I fix CVE-2007-4891?
To mitigate CVE-2007-4891, users should upgrade to a patched version of Microsoft Visual Studio that addresses this vulnerability.
What platforms are affected by CVE-2007-4891?
CVE-2007-4891 affects Microsoft Visual Studio versions 6.0 and 6.0.0.9782.
What are the potential impacts of CVE-2007-4891?
Exploitation of CVE-2007-4891 could lead to unauthorized program execution and potential compromise of sensitive data.
Is CVE-2007-4891 still a risk today?
Although CVE-2007-4891 was disclosed in 2007, systems running the affected versions of Visual Studio remain vulnerable if they have not been updated.