What is the severity of CVE-2006-3696?

CVE-2006-3696 is a denial of service vulnerability that can cause the Outpost Firewall Pro service to crash.

How do I fix CVE-2006-3696?

To fix CVE-2006-3696, you should upgrade to Outpost Firewall Pro version 3.51.759.6511 or later.

Who is affected by CVE-2006-3696?

Local users on systems running Outpost Firewall Pro versions before 3.51.759.6511 are affected by CVE-2006-3696.

What software is impacted by CVE-2006-3696?

CVE-2006-3696 impacts Agnitum Outpost Firewall version 3.5.631 and earlier.

What causes the vulnerability in CVE-2006-3696?

The vulnerability in CVE-2006-3696 is caused by the handling of long arguments passed to mshta.exe by filtnt.sys.

Vulnerability/
CVE-2006-3696

low

2.1

CWE

NVD-CWE-Other

21/7/2006

20/7/2017

CVE-2006-3696

First published: Fri Jul 21 2006(Updated: )

filtnt.sys in Outpost Firewall Pro before 3.51.759.6511 (462) allows local users to cause a denial of service (crash) via long arguments to mshta.exe.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Agnitum Outpost Firewall	=3.5.631

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2006-3696?
CVE-2006-3696 is a denial of service vulnerability that can cause the Outpost Firewall Pro service to crash.
How do I fix CVE-2006-3696?
To fix CVE-2006-3696, you should upgrade to Outpost Firewall Pro version 3.51.759.6511 or later.
Who is affected by CVE-2006-3696?
Local users on systems running Outpost Firewall Pro versions before 3.51.759.6511 are affected by CVE-2006-3696.
What software is impacted by CVE-2006-3696?
CVE-2006-3696 impacts Agnitum Outpost Firewall version 3.5.631 and earlier.
What causes the vulnerability in CVE-2006-3696?
The vulnerability in CVE-2006-3696 is caused by the handling of long arguments passed to mshta.exe by filtnt.sys.

collector/nvd-historical
collector/nvd-index
agent/author
agent/description
agent/event
agent/first-publish-date
agent/last-modified-date
agent/references
agent/remedy
agent/severity
agent/softwarecombine
agent/tags
agent/type
agent/weakness
vendor/agnitum
canonical/agnitum outpost firewall
version/agnitum outpost firewall/3.5.631

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-2006-3696?
CVE-2006-3696 is a denial of service vulnerability that can cause the Outpost Firewall Pro service to crash.
How do I fix CVE-2006-3696?
To fix CVE-2006-3696, you should upgrade to Outpost Firewall Pro version 3.51.759.6511 or later.
Who is affected by CVE-2006-3696?
Local users on systems running Outpost Firewall Pro versions before 3.51.759.6511 are affected by CVE-2006-3696.
What software is impacted by CVE-2006-3696?
CVE-2006-3696 impacts Agnitum Outpost Firewall version 3.5.631 and earlier.
What causes the vulnerability in CVE-2006-3696?
The vulnerability in CVE-2006-3696 is caused by the handling of long arguments passed to mshta.exe by filtnt.sys.

CVE-2006-3696

Remedy

Remedy

Remedy

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2006-3696?

How do I fix CVE-2006-3696?

Who is affected by CVE-2006-3696?

What software is impacted by CVE-2006-3696?

What causes the vulnerability in CVE-2006-3696?

Company

Resources

Contact

Frequently Asked Questions

What is the severity of CVE-2006-3696?

How do I fix CVE-2006-3696?

Who is affected by CVE-2006-3696?

What software is impacted by CVE-2006-3696?

What causes the vulnerability in CVE-2006-3696?