The versions of Oracle Siebel CRM installed on the remote host are affected by multiple vulnerabilities as referenced in the October 2018 CPU advisory.

  - Vulnerability in the Siebel UI Framework component of Oracle Siebel CRM (subcomponent: EAI (Apache     Log4j)). Supported versions that are affected are 18.7, 18.8 and 18.9. Easily exploitable vulnerability     allows unauthenticated attacker with network access via HTTP to compromise Siebel UI Framework. Successful     attacks of this vulnerability can result in takeover of Siebel UI Framework. (CVE-2017-5645)

  - Vulnerability in the MICROS XBRi component of Oracle Retail Applications (subcomponent: Retail (Apache     Tomcat)). Supported versions that are affected are 10.8.3, 10.8.2, 10.8.1, 10.7.0, 10.6.0 and 10.5.0.
    Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise     MICROS XBRi. Successful attacks of this vulnerability can result in unauthorized access to critical data     or complete access to all MICROS XBRi accessible data. (CVE-2018-1305)

  - Vulnerability in the Siebel UI Framework component of Oracle Siebel CRM (subcomponent: UIF Open UI).
    Supported versions that are affected are 18.7, 18.8 and 18.9. Easily exploitable vulnerability allows     unauthenticated attacker with network access via HTTP to compromise Siebel UI Framework. Successful     attacks require human interaction from a person other than the attacker and while the vulnerability is in     Siebel UI Framework, attacks may significantly impact additional products. Successful attacks of this     vulnerability can result in unauthorized update, insert or delete access to some of Siebel UI Framework     accessible data as well as unauthorized read access to a subset of Siebel UI Framework accessible data.
    (CVE-2018-3059)

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

According to the versions of the tomcat packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

  - Security constraints defined by annotations of Servlets     in Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27,     8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 were only     applied once a Servlet had been loaded. Because     security constraints defined in this way apply to the     URL pattern and any URLs below that point, it was     possible - depending on the order Servlets were loaded
    - for some security constraints not to be applied. This     could have exposed resources to users who were not     authorised to access them.(CVE-2018-1305)

  - The host name verification when using TLS with the     WebSocket client was missing. It is now enabled by     default. Versions Affected: Apache Tomcat 9.0.0.M1 to     9.0.9, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, and 7.0.35     to 7.0.88.(CVE-2018-8034)

  - The URL pattern of '' (the empty string) which exactly     maps to the context root was not correctly handled in     Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27,     8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 when used as     part of a security constraint definition. This caused     the constraint to be ignored. It was, therefore,     possible for unauthorised users to gain access to web     application resources that should have been protected.
    Only security constraints with a URL pattern of the     empty string were affected.(CVE-2018-1304)

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

The version of Oracle Secure Global Desktop installed on the remote host is 5.3 / 5.4 and is missing a security patch from the July 2018 Critical Patch Update (CPU). It is, therefore, affected by multiple vulnerabilities:

 - curl version curl 7.54.1 to and including curl 7.59.0 contains a  Heap-based Buffer Overflow vulnerability in FTP connection closing  down functionality which can lead to DoS and RCE conditions. This  vulnerability appears to have been fixed in curl < 7.54.1 and  curl >= 7.60.0. (CVE-2018-1000300)

 - Security constraints defined by annotations of Servlets in Apache  Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27, 8.0.0.RC1 to 8.0.49 and  7.0.0 to 7.0.84 were only applied once a Servlet had been loaded.  It was possible - depending on the order Servlets were loaded - for  some security constraints not to be applied. This could have exposed  resources to unauthorized users. (CVE-2018-1305)

 - ASN.1 types with a recursive definition could exceed the stack  given malicious input with excessive recursion. This could result  in a Denial Of Service attack. Fixed in OpenSSL 1.1.0h (Affected  1.1.0-1.1.0g). Fixed in OpenSSL 1.0.2o (Affected 1.0.2b-1.0.2n).
 (CVE-2018-0739)

Several security vulnerabilities have been discovered in the Tomcat servlet and JSP engine.

CVE-2018-1304 The URL pattern of '' (the empty string) which exactly maps to the context root was not correctly handled in Apache Tomcat when used as part of a security constraint definition. This caused the constraint to be ignored. It was, therefore, possible for unauthorized users to gain access to web application resources that should have been protected. Only security constraints with a URL pattern of the empty string were affected.

CVE-2018-1305 Security constraints defined by annotations of Servlets in Apache Tomcat were only applied once a Servlet had been loaded.
Because security constraints defined in this way apply to the URL pattern and any URLs below that point, it was possible - depending on the order Servlets were loaded - for some security constraints not to be applied. This could have exposed resources to users who were not authorized to access them.

For Debian 8 'Jessie', these problems have been fixed in version 8.0.14-1+deb8u12.

We recommend that you upgrade your tomcat8 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.

The version of Tomcat installed on the remote host is prior to 7.0.85. It is, therefore, affected by multiple vulnerabilities as referenced in the fixed_in_apache_tomcat_7.0.85_security-7 advisory.

  - Security constraints defined by annotations of Servlets in Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to     8.5.27, 8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 were only applied once a Servlet had been loaded. Because     security constraints defined in this way apply to the URL pattern and any URLs below that point, it was     possible - depending on the order Servlets were loaded - for some security constraints not to be applied.
    This could have exposed resources to users who were not authorised to access them. (CVE-2018-1305)

  - The URL pattern of  (the empty string) which exactly maps to the context root was not correctly handled     in Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27, 8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 when used as     part of a security constraint definition. This caused the constraint to be ignored. It was, therefore,     possible for unauthorised users to gain access to web application resources that should have been     protected. Only security constraints with a URL pattern of the empty string were affected. (CVE-2018-1304)

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

The Apache Software Foundation reports :

Security constraints defined by annotations of Servlets were only applied once a Servlet had been loaded. Because security constraints defined in this way apply to the URL pattern and any URLs below that point, it was possible - depending on the order Servlets were loaded - for some security constraints not to be applied. This could have exposed resources to users who were not authorised to access them.

The URL pattern of '' (the empty string) which exactly maps to the context root was not correctly handled when used as part of a security constraint definition. This caused the constraint to be ignored. It was, therefore, possible for unauthorised users to gain access to web application resources that should have been protected. Only security constraints with a URL pattern of the empty string were affected.

Two security vulnerabilities have been discovered in the Tomcat servlet and JSP engine.

CVE-2018-1304 The URL pattern of '' (the empty string) which exactly maps to the context root was not correctly handled in Apache Tomcat when used as part of a security constraint definition. This caused the constraint to be ignored. It was, therefore, possible for unauthorized users to gain access to web application resources that should have been protected. Only security constraints with a URL pattern of the empty string were affected.

CVE-2018-1305 Security constraints defined by annotations of Servlets in Apache Tomcat were only applied once a Servlet had been loaded.
Because security constraints defined in this way apply to the URL pattern and any URLs below that point, it was possible - depending on the order Servlets were loaded - for some security constraints not to be applied. This could have exposed resources to users who were not authorized to access them.

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

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.

Late application of security constraints can lead to resource exposure for unauthorised users :

Security constraints defined by annotations of Servlets in Apache Tomcat were only applied once a Servlet had been loaded. Because security constraints defined in this way apply to the URL pattern and any URLs below that point, it was possible - depending on the order Servlets were loaded - for some security constraints not to be applied. This could have exposed resources to users who were not authorised to access them. (CVE-2018-1305)

Incorrect handling of empty string URL in security constraints can lead to unintended exposure of resources :

The URL pattern of '' (the empty string) which exactly maps to the context root was not correctly handled in Apache Tomcat when used as part of a security constraint definition. This caused the constraint to be ignored. It was, therefore, possible for unauthorised users to gain access to web application resources that should have been protected. Only security constraints with a URL pattern of the empty string were affected. (CVE-2018-1304)

This update for tomcat fixes the following issues :

Security issues fixed :

  - CVE-2018-1305: Fixed late application of security     constraints that can lead to resource exposure for     unauthorised users (bsc#1082481).

  - CVE-2018-1304: Fixed incorrect handling of empty string     URL in security constraints that can lead to unitended     exposure of resources (bsc#1082480).

  - CVE-2017-15706: Fixed incorrect documentation of CGI     Servlet search algorithm that may lead to     misconfiguration (bsc#1078677).

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

Security Fix(es) :

  - tomcat: Incorrect handling of empty string URL in     security constraints can lead to unintended exposure of     resources (CVE-2018-1304)

  - tomcat: Late application of security constraints can     lead to resource exposure for unauthorised users     (CVE-2018-1305)

  - tomcat: Insecure defaults in CORS filter enable     'supportsCredentials' for all origins (CVE-2018-8014)

  - tomcat: Host name verification missing in WebSocket     client (CVE-2018-8034)

According to the versions of the tomcat packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

  - The URL pattern of '' (the empty string) which exactly     maps to the context root was not correctly handled in     Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27,     8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 when used as     part of a security constraint definition. This caused     the constraint to be ignored. It was, therefore,     possible for unauthorised users to gain access to web     application resources that should have been protected.
    Only security constraints with a URL pattern of the     empty string were affected.(CVE-2018-1304)

  - Security constraints defined by annotations of Servlets     in Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27,     8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 were only     applied once a Servlet had been loaded. Because     security constraints defined in this way apply to the     URL pattern and any URLs below that point, it was     possible - depending on the order Servlets were loaded
    - for some security constraints not to be applied. This     could have exposed resources to users who were not     authorised to access them.(CVE-2018-1305)

  - The host name verification when using TLS with the     WebSocket client was missing. It is now enabled by     default. Versions Affected: Apache Tomcat 9.0.0.M1 to     9.0.9, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, and 7.0.35     to 7.0.88.(CVE-2018-8034)

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

Several issues were discovered in the Tomcat servlet and JSP engine.
They could lead to unauthorized access to protected resources, denial-of-service, or information leak.

An update is now available for Red Hat JBoss Web Server 3.1 for RHEL 6 and Red Hat JBoss Web Server 3.1 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 Service Pack 2 serves as a replacement for Red Hat JBoss Web Server 3.1, and includes bug fixes, which are documented in the Release Notes document linked to in the References.

Security Fix(es) :

* apr: Out-of-bounds array deref in apr_time_exp*() functions (CVE-2017-12613)

* tomcat: Remote Code Execution via JSP Upload (CVE-2017-12615)

* tomcat: Information Disclosure when using VirtualDirContext (CVE-2017-12616)

* tomcat: Remote Code Execution bypass for CVE-2017-12615 (CVE-2017-12617)

* tomcat-native: Mishandling of client certificates can allow for OCSP check bypass (CVE-2017-15698)

* tomcat: Incorrect handling of empty string URL in security constraints can lead to unintended exposure of resources (CVE-2018-1304)

* tomcat: Late application of security constraints can lead to resource exposure for unauthorised users (CVE-2018-1305)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
212390	Oracle Siebel Server <= 18.9 (October 2018 CPU)	Nessus	Misc.	2024/12/11	2024/12/11	critical
132210	EulerOS 2.0 SP3 : tomcat (EulerOS-SA-2019-2675)	Nessus	Huawei Local Security Checks	2019/12/18	2024/4/3	high
111333	Oracle Secure Global Desktop Multiple Vulnerabilities (July 2018 CPU)	Nessus	Misc.	2018/7/25	2021/10/25	critical
111391	Debian DLA-1450-1 : tomcat8 security update	Nessus	Debian Local Security Checks	2018/7/30	2024/9/2	medium
106975	Apache Tomcat 7.0.0 < 7.0.85 multiple vulnerabilities	Nessus	Web Servers	2018/2/23	2024/5/23	medium
107043	FreeBSD : tomcat -- Security constraints ignored or applied too late (55c4233e-1844-11e8-a712-0025908740c2)	Nessus	FreeBSD Local Security Checks	2018/2/28	2025/10/27	medium
107151	Debian DLA-1301-1 : tomcat7 security update	Nessus	Debian Local Security Checks	2018/3/7	2025/10/27	medium
108597	Amazon Linux AMI : tomcat7 / tomcat8 (ALAS-2018-972)	Nessus	Amazon Linux Local Security Checks	2018/3/27	2024/12/6	medium
108742	openSUSE Security Update : tomcat (openSUSE-2018-325)	Nessus	SuSE Local Security Checks	2018/3/30	2024/11/22	medium
128266	Scientific Linux Security Update : tomcat on SL7.x x86_64 (20190806)	Nessus	Scientific Linux Local Security Checks	2019/8/27	2024/5/1	critical
129186	EulerOS 2.0 SP5 : tomcat (EulerOS-SA-2019-1992)	Nessus	Huawei Local Security Checks	2019/9/24	2024/4/23	high
112185	Debian DSA-4281-1 : tomcat8 - security update	Nessus	Debian Local Security Checks	2018/8/30	2024/8/13	high
107208	RHEL 6 / 7 : Red Hat JBoss Web Server 3.1.0 Service Pack 2 (RHSA-2018:0466)	Nessus	Red Hat Local Security Checks	2018/3/8	2023/4/25	high

检测

插件搜索

critical

high

critical

medium

medium

medium

medium

medium

medium

critical

high

high

high