Question

我在工作中遇到了一些困惑。我和一些工程师认为nessus（据我们所知是一个端口扫描器）不会关心我希望从/usr/java/apache-tomcat-5.5.33重命名我们服务器上的tomcat目录到/ usr / java / apache-tomcat。

我希望这样做可以让下次当客户喊出“漏洞！”时我们被迫升级我们的服务器时生活更轻松。

因此，如果我希望将tomcat服务器路径设为通用，那么Nessus将不会关心它。该产品（Nessus）将能够嗅出产品版本。

这是对的吗？

感谢您的帮助。

-dklotz

CNC中以下是客户向我们报告的扫描结果。

Apache Tomcat 5.5.x < 5.5.34 Multiple Vulnerabilities   Category: Web Servers
Description: 

According to its self-reported version number, the instance of Apache
Tomcat 5.5.x listening on the remote host is earlier than 5.5.34 and
is affected by multiple vulnerabilities:

  - Several weaknesses were found in the HTTP Digest
    authentication implementation. The issues are as
    follows: replay attacks are possible, server nonces
    are not checked, client nonce counts are not checked,
    'quality of protection' (qop) values are not checked, 
    realm values are not checked and the server secret is 
    a hard-coded, known string. The effect of these issues 
    is that Digest authentication is no stronger than Basic 
    authentication. (CVE-2011-1184, CVE-2011-5062, 
    CVE-2011-5063, CVE-2011-5064)

  - An error handling issue exists related to the
    MemoryUserDatabase that allows user passwords to be
    disclosed through log files. (CVE-2011-2204)

  - An input validation error exists that allows a local
    attacker to either bypass security or carry out denial
    of service attacks when the APR or NIO connectors are
    enabled. (CVE-2011-2526)

  - A component that Apache Tomcat relies on called 'jsvc' 
    contains an error in that it does not drop capabilities
    after starting and can allow access to sensitive files 
    owned by the super user. Note this vulnerability only 
    affects Linux operating systems and only when 'jsvc' is
    compiled with libpcap and the '-user' parameter is 
    used. (CVE-2011-2729)

  - Specially crafted requests are incorrectly processed by
    Tomcat and can cause the server to allow injection of 
    arbitrary AJP messages. This can lead to authentication 
    bypass and disclosure of sensitive information. Note 
    this vulnerability only occurs when the
    org.apache.jk.server.JkCoyoteHandler AJP connector is 
    not used, POST requests are accepted, and the request
    body is not processed.(CVE-2011-3190)

Note that Nessus did not actually test for the flaws but instead has
relied on the version in Tomcat's banner or error page.

    Vuln Publication Date: 6/27/2011
Plugin Publication Date: 9/26/2011
Easy to Exploit: Exploits are available
Exploit Available: true
CVSS Vector: CVSS2#AV:N/AC:L/Au:N/C:P/I:P/A:P
CVSS Base Score: 7.5
CVSS Temporal Vector: CVSS2#E:F/RL:OF/RC:C
CVSS Temporal Score: 6.2
CVE: CVE-2011-1184
CVE-2011-2204
CVE-2011-2526
CVE-2011-2729
CVE-2011-3190
CVE-2011-5062
CVE-2011-5063
CVE-2011-5064

Cross Reference: OSVDB:73429
OSVDB:73797
OSVDB:73798
OSVDB:74541
OSVDB:74818
OSVDB:76189

See Also: http://tomcat.apache.org/security-5.html#Fixed_in_Apache_Tomcat_5.5.34

Bug Traq ID: 48456
48667
49143
49353
49762

Answer 1

::从评论::

回答

这是实际的漏洞报告。如果它从tomcat横幅获得信息，它可以通过开放的Web服务端口完成，在这种情况下没有凭据，它不关心tomcat目录实际存在的位置。但这并不意味着没有凭证，只是意味着没有它们就可以得到那些信息。您可以尝试移动它并重新扫描以查看它是否检测到漏洞，或者编辑扫描并选择“策略/凭据”部分，您可以查看是否为该特定扫描指定了凭据。

Credentialed扫描具有登录信息，未经验证的扫描不具有。

我看到你也找到了Tenable Discussion Portal - 我接下来会指出你的意思！ :-)我同意乔治的最后一篇文章 - 在我一直使用的条款中“远程检查”=“未加密”。 HTH！

Nessus是否依赖或使用目录路径来确定版本？

1 个答案: