Overview 138 matches · 109 in Waratek scope · 12 protected · 4 exploited · 1 CISA KEV · 8 public PoC · 6 EPSS ≥ 0.5
138matches
109in Waratek scope79.0%
12protected8.7%
4exploited2.9%
1CISA KEV0.7%
8public PoC5.8%
6EPSS ≥ 0.54.3%
Protected by Waratek
12
8.7%
Rule in development
0
0.0%
Mitigation candidate
5
3.6%
No exploit published
92
66.7%
Outside Waratek scope
0
0.0%
Not applicable
29
21.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
12
8.7%
partly blocked
0
0.0%
not blocked
126
91.3%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 22 / year
20121
Not applicable1
Medium1
not blocked1
No public exploit1
20133
Not applicable3
Medium1
Low2
not blocked3
No public exploit3
20140
20152
Not applicable2
High1
Medium1
not blocked2
Working exploit published1
No public exploit1
20162
Not applicable2
Critical2
not blocked2
No public exploit2
20173
Not applicable3
Medium3
not blocked3
No public exploit3
20185
No exploit published4
Not applicable1
High1
Medium4
not blocked5
No public exploit5
201918
Protected by Waratek5
No exploit published8
Not applicable5
Critical3
High9
Medium6
blocked by ARMR today5
not blocked13
Forecast only2
No public exploit16
202022
Protected by Waratek2
No exploit published19
Not applicable1
Critical2
High7
Medium13
blocked by ARMR today2
not blocked20
No public exploit22
202111
Protected by Waratek1
Mitigation candidate1
No exploit published8
Not applicable1
Critical1
High3
Medium4
Low3
blocked by ARMR today1
not blocked10
Exploited1
Working exploit published1
No public exploit9
202219
Mitigation candidate1
No exploit published18
High11
Medium7
Low1
not blocked19
Proof of concept only1
No public exploit18
202322
Protected by Waratek1
Mitigation candidate2
No exploit published15
Not applicable4
Critical2
High9
Medium11
blocked by ARMR today1
not blocked21
Exploited2
Proof of concept only1
No public exploit19
202411
Protected by Waratek1
Mitigation candidate1
No exploit published7
Not applicable2
Critical1
High7
Medium3
blocked by ARMR today1
not blocked10
Exploited1
Proof of concept only1
No public exploit9
20252
No exploit published1
Not applicable1
High1
Medium1
not blocked2
No public exploit2
202617
Protected by Waratek2
No exploit published12
Not applicable3
Critical5
High7
Medium4
Low1
blocked by ARMR today2
not blocked15
Proof of concept only1
No public exploit16
20122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2019-14885 | Medium | 2020-01-23 | No exploit published | No public exploit | A flaw was found in the JBoss EAP Vault system in all versions before 7.2.6.GA. Confidential information of the system property's security attribute value is revealed in the JBoss EAP log file when executing a JBoss CLI 'reload' command. This flaw can lead to the exposure of confidential information. |
| CVE-2019-14820 | Medium | 2020-01-08 | No exploit published | No public exploit | It was found that keycloak before version 8.0.0 exposes internal adapter endpoints in org.keycloak.constants.AdapterConstants, which can be invoked via a specially-crafted URL. This vulnerability could allow an attacker to access unauthorized information. |
| CVE-2019-14843 | High | 2020-01-07 | No exploit published | No public exploit | A flaw was found in Wildfly Security Manager, running under JDK 11 or 8, that authorized requests for any requester. This flaw could be used by a malicious app deployed on the app server to access unauthorized information and possibly conduct further attacks. Versions shipped with Red Hat Jboss EAP 7 and Red Hat SSO 7 are vulnerable to this issue. |
| CVE-2019-14837 | Critical | 2020-01-07 | No exploit published | No public exploit | A flaw was found in keycloack before version 8.0.0. The owner of 'placeholder.org' domain can setup mail server on this domain and knowing only name of a client can reset password and then log in. For example, for client name 'test' the email address will be 'service-account-test@placeholder.org'. |
| CVE-2019-10174 | High | 2019-11-25 | Protected by Waratek | No public exploit | A vulnerability was found in Infinispan such that the invokeAccessibly method from the public class ReflectionUtil allows any application class to invoke private methods in any class with Infinispan's privileges. The attacker can use reflection to introduce new, malicious behavior into the application. |
| CVE-2019-10219 | Medium | 2019-11-08 | Protected by Waratek | No public exploit | A vulnerability was found in Hibernate-Validator. The SafeHtml validator annotation fails to properly sanitize payloads consisting of potentially malicious code in HTML comments and instructions. This vulnerability can result in an XSS attack. |
| CVE-2019-14838 | Medium | 2019-10-14 | No exploit published | No public exploit | A flaw was found in wildfly-core before 7.2.5.GA. The Management users with Monitor, Auditor and Deployer Roles should not be allowed to modify the runtime state of the server |
| CVE-2019-10212 | Critical | 2019-10-02 | No exploit published | No public exploit | A flaw was found in, all under 2.0.20, in the Undertow DEBUG log for io.undertow.request.security. If enabled, an attacker could abuse this flaw to obtain the user's credentials from the log files. |
| CVE-2019-4513 | High | 2019-08-26 | Not applicable | No public exploit | IBM Security Access Manager for Enterprise Single Sign-On 8.2.2 is vulnerable to an XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources. IBM X-Force ID: 164555. |
| CVE-2019-10201 | High | 2019-08-14 | No exploit published | No public exploit | It was found that Keycloak's SAML broker, versions up to 6.0.1, did not verify missing message signatures. If an attacker modifies the SAML Response and removes the <Signature> sections, the message is still accepted, and the message can be modified. An attacker could use this flaw to impersonate other users and gain access to sensitive information. |
| CVE-2019-9515 | High | 2019-08-13 | Not applicable | Forecast only | Some HTTP/2 implementations are vulnerable to a settings flood, potentially leading to a denial of service. The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame is almost equivalent in behavior to a ping. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both. |
| CVE-2019-9514 | High | 2019-08-13 | Not applicable | Forecast only | Some HTTP/2 implementations are vulnerable to a reset flood, potentially leading to a denial of service. The attacker opens a number of streams and sends an invalid request over each stream that should solicit a stream of RST_STREAM frames from the peer. Depending on how the peer queues the RST_STREAM frames, this can consume excess memory, CPU, or both. |
| CVE-2019-3800 | High | 2019-08-05 | Not applicable | No public exploit | CF CLI version prior to v6.45.0 (bosh release version 1.16.0) writes the client id and secret to its config file when the user authenticates with --client-credentials flag. A local authenticated malicious user with access to the CF CLI config file can act as that client, who is the owner of the leaked credentials. |
| CVE-2019-14379 | Critical | 2019-07-29 | Protected by Waratek | No public exploit | SubTypeValidator.java in FasterXML jackson-databind before 2.9.9.2 mishandles default typing when ehcache is used (because of net.sf.ehcache.transaction.manager.DefaultTransactionManagerLookup), leading to remote code execution. |
| CVE-2019-10184 | High | 2019-07-25 | No exploit published | No public exploit | undertow before version 2.0.23.Final is vulnerable to an information leak issue. Web apps may have their directory structures predicted through requests without trailing slashes via the api. |
| CVE-2019-3875 | Medium | 2019-06-12 | No exploit published | No public exploit | A vulnerability was found in keycloak before 6.0.2. The X.509 authenticator supports the verification of client certificates through the CRL, where the CRL list can be obtained from the URL provided in the certificate itself (CDP) or through the separately configured path. The CRL are often available over the network through unsecured protocols ('http' or 'ldap') and hence the caller should verify the signature and possibly the certification path. Keycloak currently doesn't validate signatures on CRL, which can result in a possibility of various attacks like man-in-the-middle. |
| CVE-2019-3873 | Critical | 2019-06-12 | No exploit published | No public exploit | It was found that Picketlink as shipped with Jboss Enterprise Application Platform 7.2 would accept an xinclude parameter in SAMLresponse XML. An attacker could use this flaw to send a URL to achieve cross-site scripting or possibly conduct further attacks. |
| CVE-2019-3872 | Medium | 2019-06-12 | No exploit published | No public exploit | It was found that a SAMLRequest containing a script could be processed by Picketlink versions shipped in Jboss Application Platform 7.2.x and 7.1.x. An attacker could use this to send a malicious script to achieve cross-site scripting and obtain unauthorized information or conduct further attacks. |
| CVE-2019-10157 | Medium | 2019-06-12 | Not applicable | No public exploit | It was found that Keycloak's Node.js adapter before version 4.8.3 did not properly verify the web token received from the server in its backchannel logout . An attacker with local access could use this to construct a malicious web token setting an NBF parameter that could prevent user access indefinitely. |
| CVE-2018-10934 | Medium | 2019-03-27 | No exploit published | No public exploit | A cross-site scripting (XSS) vulnerability was found in the JBoss Management Console versions before 7.1.6.CR1, 7.1.6.GA. Users with roles that can create objects in the application can exploit this to attack other privileged users. |
| CVE-2018-12023 | High | 2019-03-21 | Protected by Waratek | No public exploit | An issue was discovered in FasterXML jackson-databind prior to 2.7.9.4, 2.8.11.2, and 2.9.6. When Default Typing is enabled (either globally or for a specific property), the service has the Oracle JDBC jar in the classpath, and an attacker can provide an LDAP service to access, it is possible to make the service execute a malicious payload. |
| CVE-2018-12022 | High | 2019-03-21 | Protected by Waratek | No public exploit | An issue was discovered in FasterXML jackson-databind prior to 2.7.9.4, 2.8.11.2, and 2.9.6. When Default Typing is enabled (either globally or for a specific property), the service has the Jodd-db jar (for database access for the Jodd framework) in the classpath, and an attacker can provide an LDAP service to access, it is possible to make the service execute a malicious payload. |
| CVE-2018-14657 | High | 2018-11-13 | No exploit published | No public exploit | A flaw was found in Keycloak 4.2.1.Final, 4.3.0.Final. When TOPT enabled, an improper implementation of the Brute Force detection algorithm will not enforce its protection measures. |
| CVE-2018-14655 | Medium | 2018-11-13 | No exploit published | No public exploit | A flaw was found in Keycloak 3.4.3.Final, 4.0.0.Beta2, 4.3.0.Final. When using 'response_mode=form_post' it is possible to inject arbitrary Javascript-Code via the 'state'-parameter in the authentication URL. This allows an XSS-Attack upon succesfully login. |
| CVE-2017-1732 | Medium | 2018-08-17 | Not applicable | No public exploit | IBM Security Access Manager for Enterprise Single Sign-On 8.2.2 does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and the attacker can then obtain the cookie value by snooping the traffic. IBM X-Force ID: 134913. |
| CVE-2018-10894 | Medium | 2018-08-01 | No exploit published | No public exploit | It was found that SAML authentication in Keycloak 3.4.3.Final incorrectly authenticated expired certificates. A malicious user could use this to access unauthorized data or possibly conduct further attacks. |
| CVE-2018-10912 | Medium | 2018-07-23 | No exploit published | No public exploit | keycloak before version 4.0.0.final is vulnerable to a infinite loop in session replacement. A Keycloak cluster with multiple nodes could mishandle an expired session replacement and lead to an infinite loop. A malicious authenticated user could use this flaw to achieve Denial of Service on the server. |
| CVE-2017-8044 | Medium | 2017-11-27 | Not applicable | No public exploit | In Pivotal Single Sign-On for PCF (1.3.x versions prior to 1.3.4 and 1.4.x versions prior to 1.4.3), certain pages allow code to be injected into the DOM environment through query parameters, leading to XSS attacks. |
| CVE-2017-8041 | Medium | 2017-09-09 | Not applicable | No public exploit | In Single Sign-On for Pivotal Cloud Foundry (PCF) 1.3.x versions prior to 1.3.4 and 1.4.x versions prior to 1.4.3, a user can execute a XSS attack on certain Single Sign-On service UI pages by inputting code in the text field for an organization name. |
| CVE-2017-8040 | Medium | 2017-09-09 | Not applicable | No public exploit | In Single Sign-On for Pivotal Cloud Foundry (PCF) 1.3.x versions prior to 1.3.4 and 1.4.x versions prior to 1.4.3, an XXE (XML External Entity) attack was discovered in the Single Sign-On service dashboard. Privileged users can in some cases upload malformed XML leading to exposure of data on the Single Sign-On service broker file system. |
| CVE-2015-6854 | Critical | 2016-03-24 | Not applicable | No public exploit | The non-Domino web agents in CA Single Sign-On (aka SSO, formerly SiteMinder) R6, R12.0 before SP3 CR13, R12.0J before SP3 CR1.2, and R12.5 before CR5 allow remote attackers to cause a denial of service (daemon crash) or obtain sensitive information via a crafted request. |
| CVE-2015-6853 | Critical | 2016-03-24 | Not applicable | No public exploit | The Domino web agent in CA Single Sign-On (aka SSO, formerly SiteMinder) R6, R12.0 before SP3 CR13, R12.0J before SP3 CR1.2, R12.5 before CR5, R12.51 before CR4, and R12.52 before SP1 CR3 allows remote attackers to cause a denial of service (daemon crash) or obtain sensitive information via a crafted request. |
| CVE-2015-2215 | Medium | 2015-03-05 | Not applicable | No public exploit | Open redirect vulnerability in the Services single sign-on server helper (services_sso_server_helper) module for Drupal allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via unspecified parameters. |
| CVE-2015-0235 | High | 2015-01-28 | Not applicable | Working exploit published | Heap-based buffer overflow in the __nss_hostname_digits_dots function in glibc 2.2, and other 2.x versions before 2.18, allows context-dependent attackers to execute arbitrary code via vectors related to the (1) gethostbyname or (2) gethostbyname2 function, aka "GHOST." |
| CVE-2013-5420 | Low | 2013-12-23 | Not applicable | No public exploit | The IMS server before Ifix 6 in IBM Security Access Manager for Enterprise Single Sign-On (ISAM ESSO) 8.2 allows remote authenticated users to read log files by leveraging helpdesk privileges for a direct request. |
| CVE-2013-6745 | Low | 2013-12-22 | Not applicable | No public exploit | Cross-site scripting (XSS) vulnerability in the IMS server before Ifix 6 in IBM Security Access Manager for Enterprise Single Sign-On (ISAM ESSO) 8.2 allows remote authenticated users to inject arbitrary web script or HTML via crafted input to an unspecified dynamic web form. |
| CVE-2013-5421 | Medium | 2013-12-22 | Not applicable | No public exploit | Cross-site scripting (XSS) vulnerability in the IMS server before Ifix 6 in IBM Security Access Manager for Enterprise Single Sign-On (ISAM ESSO) 8.2 allows remote attackers to inject arbitrary web script or HTML via crafted input to an unspecified dynamic web form. |
| CVE-2012-5352 | Medium | 2012-10-09 | Not applicable | No public exploit | Java Open Single Sign-On Project Home (JOSSO) allows remote attackers to forge messages and bypass authentication via a SAML assertion that lacks a Signature element, aka a "Signature exclusion attack." |