Overview 14 matches · 1 protected · 0 exploited · 0 CISA KEV · 1 public PoC · 1 EPSS ≥ 0.5
Protected by Waratek
1
7.1%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
13
92.9%
blocked by ARMR today
1
7.1%
partly blocked
0
0.0%
not blocked
13
92.9%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
1
7.1%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
13
92.9%
split by
peak 3 / month
Jan 171
No exploit published1
High1
not blocked1
No public exploit1
Feb 171
No exploit published1
High1
not blocked1
No public exploit1
Mar 171
No exploit published1
High1
not blocked1
No public exploit1
Apr 172
Protected by Waratek1
No exploit published1
Critical1
High1
blocked by ARMR today1
not blocked1
Working exploit published1
No public exploit1
May 171
No exploit published1
High1
not blocked1
No public exploit1
Jun 171
No exploit published1
Medium1
not blocked1
No public exploit1
Jul 173
No exploit published3
High2
Low1
not blocked3
No public exploit3
Aug 172
No exploit published2
Medium2
not blocked2
No public exploit2
Sep 171
No exploit published1
Medium1
not blocked1
No public exploit1
Oct 171
No exploit published1
Medium1
not blocked1
No public exploit1
Jan 17Feb 17Mar 17Apr 17May 17Jun 17Jul 17Aug 17Sep 17Oct 17
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2017-1503 | Medium | 2017-10-10 | No exploit published | No public exploit | IBM WebSphere Application Server 7.0, 8.0, 8.5, and 9.0 is vulnerable to HTTP response splitting attacks. A remote attacker could exploit this vulnerability using specially-crafted URL to cause the server to return a split response, once the URL is clicked. This would allow the attacker to perform further attacks, such as Web cache poisoning, cross-site scripting, and possibly obtain sensitive information. IBM X-Force ID: 129578. |
| CVE-2015-0110 | Medium | 2017-09-15 | No exploit published | No public exploit | IBM Business Process Manager (aka BPM) 7.5.x, 8.0.x, and 8.5.x and WebSphere Lombardi Edition (aka WLE) 7.2.x allow remote authenticated users to bypass intended access restrictions on internal service types via vectors involving the executeServiceByName URL. |
| CVE-2017-1501 | Medium | 2017-08-18 | No exploit published | No public exploit | IBM WebSphere Application Server 8.0, 8.5, and 9.0 could provide weaker than expected security after using the Admin Console to update the web services security bindings settings. IBM X-Force ID: 129576. |
| CVE-2017-1504 | Medium | 2017-08-03 | No exploit published | No public exploit | IBM WebSphere Application Server version 9.0.0.4 could provide weaker than expected security after using the PasswordUtil command to enable AES password encryption. IBM X-Force ID: 129579. |
| CVE-2017-1382 | High | 2017-07-24 | No exploit published | No public exploit | IBM WebSphere Application Server 7.0, 8.0, 8.5, and 9.0 might create files using the default permissions instead of the customized permissions when custom startup scripts are used. A local attacker could exploit this to gain access to files with an unknown impact. IBM X-Force ID: 127153. |
| CVE-2017-1381 | Low | 2017-07-21 | No exploit published | No public exploit | IBM WebSphere Application Server Proxy Server or On-demand-router (ODR) 7.0, 8.0, 8.5, 9.0 and could allow a local attacker to obtain sensitive information, caused by stale data being cached and then served. IBM X-Force ID: 127152. |
| CVE-2015-3198 | High | 2017-07-21 | No exploit published | No public exploit | The Undertow module of WildFly 9.x before 9.0.0.CR2 and 10.x before 10.0.0.Alpha1 allows remote attackers to obtain the source code of a JSP page via a "/" at the end of a URL. |
| CVE-2016-9736 | Medium | 2017-06-08 | No exploit published | No public exploit | IBM WebSphere Application Server using malformed SOAP requests could allow a remote attacker to obtain sensitive information. |
| CVE-2017-1137 | High | 2017-05-10 | No exploit published | No public exploit | IBM WebSphere Application Server 8.0 and 8.5.5 could provide weaker than expected security. A remote attacker could exploit this weakness to obtain sensitive information and gain unauthorized access to the admin console. IBM X-Force ID: 121549. |
| CVE-2017-1194 | High | 2017-04-28 | No exploit published | No public exploit | IBM WebSphere Application Server 7.0, 8.0, 8.5, and 9.0 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts. IBM X-Force ID: 123669. |
| CVE-2017-5645 | Critical | 2017-04-17 | Protected by Waratek | Working exploit published | In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another application, a specially crafted binary payload can be sent that, when deserialized, can execute arbitrary code. |
| CVE-2017-1151 | High | 2017-03-20 | No exploit published | No public exploit | IBM WebSphere Application Server 8.0, 8.5, 8.5.5, and 9.0 using OpenID Connect (OIDC) configured with a Trust Association Interceptor (TAI) could allow a user to gain elevated privileges on the system. IBM Reference #: 1999293. |
| CVE-2016-8919 | High | 2017-02-01 | No exploit published | No public exploit | IBM WebSphere Application Server may be vulnerable to a denial of service, caused by allowing serialized objects from untrusted sources to run and cause the consumption of resources. |
| CVE-2016-9879 | High | 2017-01-06 | No exploit published | No public exploit | An issue was discovered in Pivotal Spring Security before 3.2.10, 4.1.x before 4.1.4, and 4.2.x before 4.2.1. Spring Security does not consider URL path parameters when processing security constraints. By adding a URL path parameter with an encoded "/" to a request, an attacker may be able to bypass a security constraint. The root cause of this issue is a lack of clarity regarding the handling of path parameters in the Servlet Specification. Some Servlet containers include path parameters in the value returned for getPathInfo() and some do not. Spring Security uses the value returned by getPathInfo() as part of the process of mapping requests to security constraints. The unexpected presence of path parameters can cause a constraint to be bypassed. Users of Apache Tomcat (all current versions) are not affected by this vulnerability since Tomcat follows the guidance previously provided by the Servlet Expert group and strips path parameters from the value returned by getContextPath(), getServletPath(), and getPathInfo(). Users of other Servlet containers based on Apache Tomcat may or may not be affected depending on whether or not the handling of path parameters has been modified. Users of IBM WebSphere Application Server 8.5.x are known to be affected. Users of other containers that implement the Servlet specification may be affected. |