Overview 8 matches · 0 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
8matches
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
8
100.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
8
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
8
100.0%
split by
peak 3 / month
Oct 171
No exploit published1
High1
not blocked1
No public exploit1
Nov 170
Dec 170
Jan 180
Feb 180
Mar 181
No exploit published1
Medium1
not blocked1
No public exploit1
Apr 180
May 180
Jun 180
Jul 181
No exploit published1
Critical1
not blocked1
No public exploit1
Aug 180
Sep 180
Oct 180
Nov 181
No exploit published1
High1
not blocked1
No public exploit1
Dec 180
Jan 193
No exploit published3
High2
Medium1
not blocked3
No public exploit3
Feb 190
Mar 191
No exploit published1
High1
not blocked1
No public exploit1
Nov 17Jan 18Mar 18May 18Jul 18Sep 18Nov 18Jan 19Mar 19
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2019-0212 | High | 2019-03-28 | No exploit published | No public exploit | In all previously released Apache HBase 2.x versions (2.0.0-2.0.4, 2.1.0-2.1.3), authorization was incorrectly applied to users of the HBase REST server. Requests sent to the HBase REST server were executed with the permissions of the REST server itself, not with the permissions of the end-user. This issue is only relevant when HBase is configured with Kerberos authentication, HBase authorization is enabled, and the REST server is configured with SPNEGO authentication. This issue does not extend beyond the HBase REST server. |
| CVE-2019-1003004 | High | 2019-01-22 | No exploit published | No public exploit | An improper authorization vulnerability exists in Jenkins 2.158 and earlier, LTS 2.150.1 and earlier in core/src/main/java/hudson/security/AuthenticationProcessingFilter2.java that allows attackers to extend the duration of active HTTP sessions indefinitely even though the user account may have been deleted in the mean time. |
| CVE-2019-1003003 | High | 2019-01-22 | No exploit published | No public exploit | An improper authorization vulnerability exists in Jenkins 2.158 and earlier, LTS 2.150.1 and earlier in core/src/main/java/hudson/security/TokenBasedRememberMeServices2.java that allows attackers with Overall/RunScripts permission to craft Remember Me cookies that would never expire, allowing e.g. to persist access to temporarily compromised user accounts. |
| CVE-2018-1000408 | Medium | 2019-01-09 | No exploit published | No public exploit | A denial of service vulnerability exists in Jenkins 2.145 and earlier, LTS 2.138.1 and earlier in core/src/main/java/hudson/security/HudsonPrivateSecurityRealm.java that allows attackers without Overall/Read permission to access a specific URL on instances using the built-in Jenkins user database security realm that results in the creation of an ephemeral user record in memory. |
| CVE-2018-14637 | High | 2018-11-30 | No exploit published | No public exploit | The SAML broker consumer endpoint in Keycloak before version 4.6.0.Final ignores expiration conditions on SAML assertions. An attacker can exploit this vulnerability to perform a replay attack. |
| CVE-2017-2589 | Critical | 2018-07-26 | No exploit published | No public exploit | It was discovered that the hawtio servlet 1.4 uses a single HttpClient instance to proxy requests with a persistent cookie store (cookies are stored locally and are not passed between the client and the end URL) which means all clients using that proxy are sharing the same cookies. |
| CVE-2018-1000107 | Medium | 2018-03-13 | No exploit published | No public exploit | An improper authorization vulnerability exists in Jenkins Job and Node Ownership Plugin 0.11.0 and earlier in OwnershipDescription.java, JobOwnerJobProperty.java, and OwnerNodeProperty.java that allow an attacker with Job/Configure or Computer/Configure permission and without Ownership related permissions to override ownership metadata. |
| CVE-2017-12160 | High | 2017-10-26 | No exploit published | No public exploit | It was found that Keycloak oauth would permit an authenticated resource to obtain an access/refresh token pair from the authentication server, permitting indefinite usage in the case of permission revocation. An attacker on an already compromised resource could use this flaw to grant himself continued permissions and possibly conduct further attacks. |