openVAS扫描新的实例失败testing(可能的误报)如何debugging插件

我已经从primefaces公司的YUM回购安装了openVAS ,这似乎都运行奇妙,但是我看到一个单一的“安全漏洞”,这是OpenVAS检测到“阿罗拉”安装在系统上,(它不是)

对于“Arora通用名称SSL证书欺骗漏洞(Linux)”,我得到了积极的结果。

我拉起脚本,似乎是search文件名“arora”的二进制文件; (

modName = find_file(file_name:"arora", file_path:"/usr/bin/", useregex:TRUE, regexpar:"$", sock:sock); 

然而,有问题的目标没有安装名为arora的二进制文件,甚至没有任何带有文件的文件,甚至在不区分大小写的search中使用子string“arora”。

 [root@52-56-149-11 ~]# locate Arora [root@52-56-149-11 ~]# locate rora [root@52-56-149-11 ~]# locate arora [root@52-56-149-11 ~]# find / | grep -i arora 

一切都没有回报。

我可以手工运行这个testing,并检查值或东西?

(我是openvas nasl脚本的新手,所以任何指向文档的地方都会有帮助,我查看了1.0.1纲要中的故障排除指南,但是我无法确定如何将SSH凭证作为参数发送到nasl脚本)

我已安装的testing副本的完整源代码如下;

 ############################################################################### # Openvas Vulnerability Test # $id: secpod_arora_cn_ssl_cert_spoofing_vuln_lin.nasl 2011-12-15 14:01:47z dec $ # # Arora Common Name SSL Certificate Spoofing Vulnerability (Linux) # # Authors: # Madhuri D<[email protected] <mailto:[email protected]>> # # Copyright: # Copyright (c) 2011 SecPod,http://www.secpod.com <http://www.secpod.com/> # # This program is free software; you can redistribute it and/or modify # it under the terms of the gnu general public license version 2 # (or any later version), as published by the free software foundation. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. ############################################################################### if(description) { script_id(902764); script_version("$Revision$"); script_cve_id("CVE-2011-3367"); script_bugtraq_id(49925); script_tag(name:"cvss_base", value:"5.0"); script_tag(name:"cvss_base_vector", value:"AV:N/AC:L/Au:N/C:N/I:P/A:N"); script_tag(name:"risk_factor", value:"Medium"); script_tag(name:"last_modification", value:"$Date$"); script_tag(name:"creation_date", value:"2011-12-15 14:01:47 +0530 (Thu, 15 Dec 2011)"); script_name("Arora Common Name SSL Certificate Spoofing Vulnerability (Linux)"); desc = " Overview: This host is installed with Arora and is prone common name SSL certificate spoofing vulnerability. Vulnerability Insight: The flaw is caused due to not using a certain font when rendering certificate fields in a security dialog. Impact: Successful exploitation will allow remote attackers to spoof the common name (CN) of a certificate via rich text. Impact Level: Application. Affected Software : Arora version 0.11 and prior Fix: No solution or patch is available as on 15th December 2011. Information regarding this issue will be updated once the solution details are available For updates refer,http://code.google.com/p/arora/downloads/list References: http://secunia.com/advisories/46269 http://www.securityfocus.com/archive/1/520041 https://bugzilla.redhat.com/show_bug.cgi?id=746875 http://archives.neohapsis.com/archives/fulldisclosure/2011-10/att-0353/NDSA20111003.txt.asc "; script_description(desc); script_summary("Check for the version of Arora"); script_category(ACT_GATHER_INFO); script_copyright("Copyright (C) 2011 SecPod"); script_family("General"); script_dependencies("find_service.nes"); script_mandatory_keys("login/SSH/success"); exit(0); } include("ssh_func.inc"); include("version_func.inc"); ## Open SSH Login connection sock = ssh_login_or_reuse_connection(); if(!sock){ exit(0); } ## Confirm Linux, as SSH can be instslled on Windows as well result = ssh_cmd(socket:sock, cmd:"uname"); if("Linux">!< result){ exit(0); } grep = find_bin(prog_name:"grep", sock:sock); grep = chomp(grep[0]); garg[0] = "-o"; garg[1] = "-m1"; garg[2] = "-a"; garg[3] = string("[0]\\.[0-9][0-9]\\.[0-9]"); ## Getting arora file path modName = find_file(file_name:"arora", file_path:"/usr/bin/", useregex:TRUE, regexpar:"$", sock:sock); foreach binaryName (modName) { binaryName = chomp(binaryName); arg = garg[0] + " " + garg[1] + " " + garg[2] + " " + raw_string(0x22) + garg[3] + raw_string(0x22) + " " + binaryName; } ## Grep the version arrVer = get_bin_version(full_prog_name:grep, version_argv:arg, ver_pattern:"([0-9.]+)", sock:sock); if(arrVer) { ## Check the arora version if(version_is_less_equal(version:arrVer[0], test_version:"0.11.0")){ security_warning(0); } } ssh_close_connection(); [1]: http://wald.intevation.org/scm/viewvc.php/trunk/openvas-plugins/scripts/secpod_arora_cn_ssl_cert_spoofing_vuln_lin.nasl?root=openvas&view=markup 

大多数NASL脚本足够简单,可以使用“打印”语句进行debugging。 使用NASLfunctiondisplay( var )在屏幕上显示variables的内容。

然后对目标运行脚本

 nasl -s -t ipaddress myscript.nasl 

请记住,这不会运行依赖关系。 如果testing需要依赖性的影响,则可以使用-k kbfile选项指定自己的知识库文件。

如果你想全面追踪每一个函数调用,请求和响应; 那么还要添加-a开关。 这可以是非常有用的,但产生大量的输出。

熟悉手册 。 这是大多数可靠的,但不要指望它的一切都是事实准确,完整或performance出自我参照的完整性:-)