Unscored severity · published Jul 21, 2006
CVE-2006-3696
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
–
CVSS
0.7%
EPSS
No
On KEV
Description
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.
Exploitation
Is it being used?
Exploit prediction (EPSS)0.7% · higher than 54% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
OF
Outpost Firewall · Agnitum
3.5.631 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2006-3696
CVE.org
https://www.cve.org/CVERecord?id=CVE-2006-3696
Patch
http://secunia.com/advisories/21095
securityreason.com
http://securityreason.com/securityalert/1247
Patch
http://www.securityfocus.com/archive/1/440427
Patch
http://www.securityfocus.com/bid/19026
www.vupen.com
http://www.vupen.com/english/advisories/2006/2853
exchange.xforce.ibmcloud.com
https://exchange.xforce.ibmcloud.com/vulnerabilities/27840
More from Outpost Firewall
–
CVE-2007-5042
Outpost Firewall Pro 4.0.1025.7828 does not properly validate certain parameters to System Service Descriptor Table (SSDT) function handlers, which allows local users to cause a…
–
CVE-2007-3086
Unrestricted critical resource lock in Agnitum Outpost Firewall PRO 4.0 1007.591.145 and earlier allows local users to cause a denial of service (system hang) by capturing the…
–
CVE-2006-7160
The Sandbox.sys driver in Outpost Firewall PRO 4.0, and possibly earlier versions, does not validate arguments to hooked SSDT functions, which allows local users to cause a denial…
–
CVE-2007-0333
Agnitum Outpost Firewall PRO 4.0 allows local users to bypass access restrictions and insert Trojan horse drivers into the product's installation directory by creating links using…
–
CVE-2006-5721
The \Device\SandBox driver in Outpost Firewall PRO 4.0 (964.582.059) allows local users to cause a denial of service (system crash) via an invalid argument to the DeviceIoControl…