Comments for Badware Watch http://www.badwarewatch.com Keeping you on top of Badware! Sun, 16 Mar 2008 10:42:12 +0000 http://wordpress.org/?v=2.9.1 hourly 1 Comment on CVE-2008-0921 (beContent) by Alfonso Pierantonio http://www.badwarewatch.com/cve-2008-0921-becontent.php/comment-page-1#comment-107 Alfonso Pierantonio Sun, 16 Mar 2008 10:42:12 +0000 http://www.badwarewatch.com/cve-2008-0921-becontent.php#comment-107 Hello, I am the project manager of beContent, I would like to let you know that new versions of beContent have been released to cope with the vulnerability issue you have announced. Would be great whether you can announce this. Thank you in advance, Alfonso Hello,

I am the project manager of beContent, I would like to let you know that new versions of beContent have been released to cope with the vulnerability issue you have announced. Would be great whether you can announce this.

Thank you in advance,
Alfonso

]]> Comment on CVE-2007-6017 (Backup Exec for Windows Server) by Kuanglien http://www.badwarewatch.com/cve-2007-6017-backup-exec-for-windows-server-3.php/comment-page-1#comment-81 Kuanglien Tue, 04 Mar 2008 17:13:16 +0000 http://www.badwarewatch.com/cve-2007-6017-backup-exec-for-windows-server-3.php#comment-81 "For a successful attack a victim has to use Internet Explorer to visit a specially crafted web page. Since the vulnerable systems are servers, Symantec classifies the risk of exploitation as low – assuming that administrators don't normally use servers to browse the web" “For a successful attack a victim has to use Internet Explorer to visit a specially crafted web page. Since the vulnerable systems are servers, Symantec classifies the risk of exploitation as low – assuming that administrators don’t normally use servers to browse the web”

]]> Comment on CVE-2008-0700 (CruxCMS) by Crux CMS http://www.badwarewatch.com/cve-2008-0700-cruxcms-2.php/comment-page-1#comment-63 Crux CMS Sun, 24 Feb 2008 00:36:36 +0000 http://www.badwarewatch.com/cve-2008-0700-cruxcms-2.php#comment-63 This has now been fixed in the latest release This has now been fixed in the latest release

]]>