An update is now available for Red Hat JBoss Web Server 3 for RHEL 7.

Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

Red Hat JBoss Web Server is a fully integrated and certified set of components for hosting Java web applications. It is comprised of the Apache HTTP Server, the Apache Tomcat Servlet container, Apache Tomcat Connector (mod_jk), JBoss HTTP Connector (mod_cluster), Hibernate, and the Tomcat Native library.

This release of Red Hat JBoss Web Server 3.1.0 serves as a replacement for Red Hat JBoss Web Server 3.0.3, and includes enhancements.

Security Fix(es) :

* It was reported that the Tomcat init script performed unsafe file handling, which could result in local privilege escalation.
(CVE-2016-1240)

* It was discovered that the Tomcat packages installed certain configuration files read by the Tomcat initialization script as writeable to the tomcat group. A member of the group or a malicious web application deployed on Tomcat could use this flaw to escalate their privileges. (CVE-2016-6325)

* The JmxRemoteLifecycleListener was not updated to take account of Oracle's fix for CVE-2016-3427. JMXRemoteLifecycleListener is only included in EWS 2.x and JWS 3.x source distributions. If you deploy a Tomcat instance built from source, using the EWS 2.x, or JWS 3.x distributions, an attacker could use this flaw to launch a remote code execution attack on your deployed instance. (CVE-2016-8735)

* A denial of service vulnerability was identified in Commons FileUpload that occurred when the length of the multipart boundary was just below the size of the buffer (4096 bytes) used to read the uploaded file if the boundary was the typical tens of bytes long.
(CVE-2016-3092)

* It was discovered that the code that parsed the HTTP request line permitted invalid characters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response. By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack, or obtain sensitive information from requests other then their own. (CVE-2016-6816)

* A bug was discovered in the error handling of the send file code for the NIO HTTP connector. This led to the current Processor object being added to the Processor cache multiple times allowing information leakage between requests including, and not limited to, session ID and the response body. (CVE-2016-8745)

* The Realm implementations did not process the supplied password if the supplied user name did not exist. This made a timing attack possible to determine valid user names. Note that the default configuration includes the LockOutRealm which makes exploitation of this vulnerability harder. (CVE-2016-0762)

* It was discovered that a malicious web application could bypass a configured SecurityManager via a Tomcat utility method that was accessible to web applications. (CVE-2016-5018)

* It was discovered that when a SecurityManager is configured Tomcat's system property replacement feature for configuration files could be used by a malicious web application to bypass the SecurityManager and read system properties that should not be visible. (CVE-2016-6794)

* It was discovered that a malicious web application could bypass a configured SecurityManager via manipulation of the configuration parameters for the JSP Servlet. (CVE-2016-6796)

* It was discovered that it was possible for a web application to access any global JNDI resource whether an explicit ResourceLink had been configured or not. (CVE-2016-6797)

The CVE-2016-6325 issue was discovered by Red Hat Product Security.

Enhancement(s) :

* This enhancement update adds the Red Hat JBoss Web Server 3.1.0 packages to Red Hat Enterprise Linux 7. These packages provide a number of enhancements over the previous version of Red Hat JBoss Web Server. (JIRA#JWS-268)

An update is now available for Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 5.

Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

Red Hat JBoss Enterprise Application Platform is a platform for Java applications based on the JBoss Application Server.

This release of Red Hat JBoss Enterprise Application Platform 6.4.16 serves as a replacement for Red Hat JBoss Enterprise Application Platform 6.4.15, and includes bug fixes and enhancements, which are documented in the Release Notes document linked to in the References.

Security Fix(es) :

* It was found that the log file viewer in Red Hat JBoss Enterprise Application 6 and 7 allows arbitrary file read to authenticated user via path traversal. (CVE-2017-2595)

* It was discovered that a malicious web application could bypass a configured SecurityManager via a Tomcat utility method that was accessible to web applications. (CVE-2016-5018)

* It was discovered that a malicious web application could bypass a configured SecurityManager via manipulation of the configuration parameters for the JSP Servlet. (CVE-2016-6796)

The following packages have been upgraded to a later upstream version:
tomcat (7.0.76).

Security Fix(es) :

  - The Realm implementations did not process the supplied     password if the supplied user name did not exist. This     made a timing attack possible to determine valid user     names. Note that the default configuration includes the     LockOutRealm which makes exploitation of this     vulnerability harder. (CVE-2016-0762)

  - It was discovered that a malicious web application could     bypass a configured SecurityManager via a Tomcat utility     method that was accessible to web applications.
    (CVE-2016-5018)

  - It was discovered that when a SecurityManager was     configured, Tomcat's system property replacement feature     for configuration files could be used by a malicious web     application to bypass the SecurityManager and read     system properties that should not be visible.
    (CVE-2016-6794)

  - It was discovered that a malicious web application could     bypass a configured SecurityManager via manipulation of     the configuration parameters for the JSP Servlet.
    (CVE-2016-6796)

  - It was discovered that it was possible for a web     application to access any global JNDI resource whether     an explicit ResourceLink had been configured or not.
    (CVE-2016-6797)

The version of Tomcat installed on the remote host is prior to 8.5.5. It is, therefore, affected by multiple vulnerabilities as referenced in the fixed_in_apache_tomcat_8.5.5_and_8.0.37_security-8 advisory.

  - The ResourceLinkFactory implementation in Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to     8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to 6.0.45 did not limit web application access to global JNDI resources     to those resources explicitly linked to the web application. Therefore, it was possible for a web     application to access any global JNDI resource whether an explicit ResourceLink had been configured or     not. (CVE-2016-6797)

  - A malicious web application running on Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to     8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to 6.0.45 was able to bypass a configured SecurityManager via     manipulation of the configuration parameters for the JSP Servlet. (CVE-2016-6796)

  - When a SecurityManager is configured, a web application's ability to read system properties should be     controlled by the SecurityManager. In Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to     8.0.36, 7.0.0 to 7.0.70, 6.0.0 to 6.0.45 the system property replacement feature for configuration files     could be used by a malicious web application to bypass the SecurityManager and read system properties that     should not be visible. (CVE-2016-6794)

  - In Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to     6.0.45 a malicious web application was able to bypass a configured SecurityManager via a Tomcat utility     method that was accessible to web applications. (CVE-2016-5018)

  - The Realm implementations in Apache Tomcat versions 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to     8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to 6.0.45 did not process the supplied password if the supplied user     name did not exist. This made a timing attack possible to determine valid user names. Note that the     default configuration includes the LockOutRealm which makes exploitation of this vulnerability harder.
    (CVE-2016-0762)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Multiple security vulnerabilities have been discovered in the Tomcat servlet and JSP engine, which may result in possible timing attacks to determine valid user names, bypass of the SecurityManager, disclosure of system properties, unrestricted access to global resources, arbitrary file overwrites, and potentially escalation of privileges.

In addition this update further hardens Tomcat's init and maintainer scripts to prevent possible privilege escalations. Thanks to Paul Szabo for the report.

This is probably the last security update of Tomcat 6 which will reach its end-of-life exactly in one month. We strongly recommend to switch to another supported version such as Tomcat 7 at your earliest convenience.

For Debian 7 'Wheezy', these problems have been fixed in version 6.0.45+dfsg-1~deb7u3.

We recommend that you upgrade your tomcat6 packages.

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Multiple security vulnerabilities have been discovered in the Tomcat servlet and JSP engine, which may result in possible timing attacks to determine valid user names, bypass of the SecurityManager, disclosure of system properties, unrestricted access to global resources, arbitrary file overwrites, and potentially escalation of privileges.

In addition this update further hardens Tomcat's init and maintainer scripts to prevent possible privilege escalations. Thanks to Paul Szabo for the report.

For Debian 7 'Wheezy', these problems have been fixed in version 7.0.28-4+deb7u7.

We recommend that you upgrade your tomcat7 packages.

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

This update for Tomcat provides the following fixes :

Feature changes :

The embedded Apache Commons DBCP component was updated to version 2.0.
(bsc#1010893 fate#321029)

Security fixes :

  - CVE-2016-0762: Realm Timing Attack (bsc#1007854)

  - CVE-2016-5018: Security Manager Bypass (bsc#1007855)

  - CVE-2016-6794: System Property Disclosure (bsc#1007857)

  - CVE-2016-6796: Manager Bypass (bsc#1007858)

  - CVE-2016-6797: Unrestricted Access to Global Resources     (bsc#1007853)

  - CVE-2016-8735: Remote code execution vulnerability in     JmxRemoteLifecycleListener (bsc#1011805)

  - CVE-2016-6816: HTTP Request smuggling vulnerability due     to permitting invalid character in HTTP requests     (bsc#1011812)

Bugs fixed :

  - Fixed StringIndexOutOfBoundsException in     WebAppClassLoaderBase.filter(). (bsc#974407)

  - Fixed a deployment error in the examples webapp by     changing the context.xml format to the new one     introduced by Tomcat 8. (bsc#1004728)

  - Enabled optional setenv.sh script. See section '(3.4)     Using the 'setenv' script' in     http://tomcat.apache.org/tomcat-8.0-doc/RUNNING.txt.
    (bsc#1002639)

  - Fixed regression caused by CVE-2016-6816.

This update supplies the new packages apache-commons-pool2 and apache-commons-dbcp in version 2 to allow tomcat to use the DBCP 2.0 interface.

This update was imported from the SUSE:SLE-12-SP1:Update update project.

This update for tomcat fixes the following issues :

Feature changes :

The embedded Apache Commons DBCP component was updated to version 2.0.
(bsc#1010893 fate#321029)

Security fixes :

  - CVE-2016-0762: Realm Timing Attack (bsc#1007854)

  - CVE-2016-5018: Security Manager Bypass (bsc#1007855)

  - CVE-2016-6794: System Property Disclosure (bsc#1007857)

  - CVE-2016-6796: Security Manager Bypass (bsc#1007858)

  - CVE-2016-6797: Unrestricted Access to Global Resources     (bsc#1007853)

  - CVE-2016-8735: Remote code execution vulnerability in     JmxRemoteLifecycleListener (bsc#1011805)

  - CVE-2016-6816: HTTP Request smuggling vulnerability due     to permitting invalid character in HTTP requests     (bsc#1011812)

Bug fixes :

  - Enabled optional setenv.sh script. See section '(3.4)     Using the 'setenv' script' in     http://tomcat.apache.org/tomcat-8.0-doc/RUNNING.txt.
    (bsc#1002639)

This update supplies the new packages apache-commons-pool2 and apache-commons-dbcp in version 2 to allow tomcat to use the DBCP 2.0 interface.

This update was imported from the SUSE:SLE-12-SP2:Update update project.

The remote Ubuntu 14.04 LTS / 16.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-3177-1 advisory.

    It was discovered that the Tomcat realm implementations incorrectly handled passwords when a username     didn't exist. A remote attacker could possibly use this issue to enumerate usernames. This issue only     applied to Ubuntu 12.04 LTS, Ubuntu 14.04 LTS and Ubuntu 16.04 LTS. (CVE-2016-0762)

    Alvaro Munoz and Alexander Mirosh discovered that Tomcat incorrectly limited use of a certain utility     method. A malicious application could possibly use this to bypass Security Manager restrictions. This     issue only applied to Ubuntu 12.04 LTS, Ubuntu 14.04 LTS and Ubuntu 16.04 LTS. (CVE-2016-5018)

    It was discovered that Tomcat did not protect applications from untrusted data in the HTTP_PROXY     environment variable. A remote attacker could possibly use this issue to redirect outbound traffic to an     arbitrary proxy server. This issue only applied to Ubuntu 12.04 LTS, Ubuntu 14.04 LTS and Ubuntu 16.04     LTS. (CVE-2016-5388)

    It was discovered that Tomcat incorrectly controlled reading system properties. A malicious application     could possibly use this to bypass Security Manager restrictions. This issue only applied to Ubuntu 12.04     LTS, Ubuntu 14.04 LTS and Ubuntu 16.04 LTS. (CVE-2016-6794)

    It was discovered that Tomcat incorrectly controlled certain configuration parameters. A malicious     application could possibly use this to bypass Security Manager restrictions. This issue only applied to     Ubuntu 12.04 LTS, Ubuntu 14.04 LTS and Ubuntu 16.04 LTS. (CVE-2016-6796)

    It was discovered that Tomcat incorrectly limited access to global JNDI resources. A malicious application     could use this to access any global JNDI resource without an explicit ResourceLink. This issue only     applied to Ubuntu 12.04 LTS, Ubuntu 14.04 LTS and Ubuntu 16.04 LTS. (CVE-2016-6797)

    Regis Leroy discovered that Tomcat incorrectly filtered certain invalid characters from the HTTP request     line. A remote attacker could possibly use this issue to inject data into HTTP responses. (CVE-2016-6816)

    Pierre Ernst discovered that the Tomcat JmxRemoteLifecycleListener did not implement a recommended fix. A     remote attacker could possibly use this issue to execute arbitrary code. (CVE-2016-8735)

    It was discovered that Tomcat incorrectly handled error handling in the send file code. A remote attacker     could possibly use this issue to access information from other requests. (CVE-2016-8745)

    Paul Szabo discovered that the Tomcat package incorrectly handled upgrades and removals. A local attacker     could possibly use this issue to obtain root privileges. (CVE-2016-9774, CVE-2016-9775)

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 6 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2017:0455 advisory.

    Red Hat JBoss Web Server is a fully integrated and certified set of components for hosting Java web     applications. It is comprised of the Apache HTTP Server, the Apache Tomcat Servlet container, Apache     Tomcat Connector (mod_jk), JBoss HTTP Connector (mod_cluster), Hibernate, and the Tomcat Native library.

    This release of Red Hat JBoss Web Server 3.1.0 serves as a replacement for Red Hat JBoss Web Server 3.0.3,     and includes enhancements.

    Security Fix(es):

    * It was reported that the Tomcat init script performed unsafe file handling, which could result in local     privilege escalation. (CVE-2016-1240)

    * It was discovered that the Tomcat packages installed certain configuration files read by the Tomcat     initialization script as writeable to the tomcat group. A member of the group or a malicious web     application deployed on Tomcat could use this flaw to escalate their privileges. (CVE-2016-6325)

    * The JmxRemoteLifecycleListener was not updated to take account of Oracle's fix for CVE-2016-3427.
    JMXRemoteLifecycleListener is only included in EWS 2.x and JWS 3.x source distributions. If you deploy a     Tomcat instance built from source, using the EWS 2.x, or JWS 3.x distributions, an attacker could use this     flaw to launch a remote code execution attack on your deployed instance. (CVE-2016-8735)

    * A denial of service vulnerability was identified in Commons FileUpload that occurred when the length of     the multipart boundary was just below the size of the buffer (4096 bytes) used to read the uploaded file     if the boundary was the typical tens of bytes long. (CVE-2016-3092)

    * It was discovered that the code that parsed the HTTP request line permitted invalid characters. This     could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a     different interpretation, to inject data into the HTTP response. By manipulating the HTTP response the     attacker could poison a web-cache, perform an XSS attack, or obtain sensitive information from requests     other then their own. (CVE-2016-6816)

    * A bug was discovered in the error handling of the send file code for the NIO HTTP connector. This led to     the current Processor object being added to the Processor cache multiple times allowing information     leakage between requests including, and not limited to, session ID and the response body. (CVE-2016-8745)

    * The Realm implementations did not process the supplied password if the supplied user name did not exist.
    This made a timing attack possible to determine valid user names. Note that the default configuration     includes the LockOutRealm which makes exploitation of this vulnerability harder. (CVE-2016-0762)

    * It was discovered that a malicious web application could bypass a configured SecurityManager via a     Tomcat utility method that was accessible to web applications. (CVE-2016-5018)

    * It was discovered that when a SecurityManager is configured Tomcat's system property replacement feature     for configuration files could be used by a malicious web application to bypass the SecurityManager and     read system properties that should not be visible. (CVE-2016-6794)

    * It was discovered that a malicious web application could bypass a configured SecurityManager via     manipulation of the configuration parameters for the JSP Servlet. (CVE-2016-6796)

    * It was discovered that it was possible for a web application to access any global JNDI resource whether     an explicit ResourceLink had been configured or not. (CVE-2016-6797)

    The CVE-2016-6325 issue was discovered by Red Hat Product Security.

    Enhancement(s):

    This enhancement update adds the Red Hat JBoss Web Server 3.1.0 packages to Red Hat Enterprise Linux 6.
    These packages provide a number of enhancements over the previous version of Red Hat JBoss Web Server.
    (JIRA#JWS-267)

    Users of Red Hat JBoss Web Server are advised to upgrade to these updated packages, which add this     enhancement.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
97596	RHEL 7 : Red Hat JBoss Web Server 3.1.0 (RHSA-2017:0456)	Nessus	Red Hat Local Security Checks	2017/3/8	2023/5/14	critical
100982	RHEL 5 : JBoss EAP (RHSA-2017:1550)	Nessus	Red Hat Local Security Checks	2017/6/22	2025/12/15	critical
102664	Scientific Linux Security Update : tomcat on SL7.x (noarch) (20170802)	Nessus	Scientific Linux Local Security Checks	2017/8/22	2025/11/26	critical
94578	Apache Tomcat 8.5.0 < 8.5.5 multiple vulnerabilities	Nessus	Web Servers	2016/11/4	2026/1/20	critical
95454	Debian DLA-728-1 : tomcat6 security update	Nessus	Debian Local Security Checks	2016/12/2	2026/1/15	critical
95455	Debian DLA-729-1 : tomcat7 security update	Nessus	Debian Local Security Checks	2016/12/2	2026/1/15	critical
95790	openSUSE Security Update : tomcat (openSUSE-2016-1455)	Nessus	SuSE Local Security Checks	2016/12/14	2026/1/14	critical
95791	openSUSE Security Update : tomcat (openSUSE-2016-1456)	Nessus	SuSE Local Security Checks	2016/12/14	2026/1/14	critical
96720	Ubuntu 14.04 LTS / 16.04 LTS : Tomcat vulnerabilities (USN-3177-1)	Nessus	Ubuntu Local Security Checks	2017/1/24	2024/8/27	critical
97595	RHEL 6 : Red Hat JBoss Web Server 3.1.0 (RHSA-2017:0455)	Nessus	Red Hat Local Security Checks	2017/3/8	2024/11/4	critical

检测

插件搜索

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical