Overview 13 matches · 5 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 1 public PoC · 0 EPSS ≥ 0.5
13matches
5in Waratek scope38.5%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
1public PoC7.7%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
5
38.5%
Outside Waratek scope
0
0.0%
Not applicable
8
61.5%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
13
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
1
7.7%
Proof of concept only
2
15.4%
Forecast only
0
0.0%
No public exploit
10
76.9%
split by
peak 5 / year
20142
Not applicable2
Medium2
not blocked2
Working exploit published1
No public exploit1
20150
20160
20171
No exploit published1
Medium1
not blocked1
No public exploit1
20182
No exploit published2
Medium2
not blocked2
No public exploit2
20191
Not applicable1
Medium1
not blocked1
No public exploit1
20201
Not applicable1
Medium1
not blocked1
No public exploit1
20210
20221
Not applicable1
Medium1
not blocked1
No public exploit1
20235
No exploit published2
Not applicable3
Medium5
not blocked5
Proof of concept only2
No public exploit3
2014201520162017201820192020202120222023
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2023-37945 | Medium | 2023-07-12 | No exploit published | No public exploit | A missing permission check in Jenkins SAML Single Sign On(SSO) Plugin 2.1.0 through 2.3.0 (both inclusive) allows attackers with Overall/Read permission to download a string representation of the current security realm. |
| CVE-2023-32993 | Medium | 2023-05-16 | No exploit published | No public exploit | Jenkins SAML Single Sign On(SSO) Plugin 2.0.2 and earlier does not perform hostname validation when connecting to miniOrange or the configured IdP to retrieve SAML metadata, which could be abused using a man-in-the-middle attack to intercept these connections. |
| CVE-2023-1093 | Medium | 2023-03-27 | Not applicable | Proof of concept only | The OAuth Single Sign On WordPress plugin before 6.24.2 does not have CSRF checks when discarding Identify providers (IdP), which could allow attackers to make logged in admins delete all IdP via a CSRF attack |
| CVE-2023-1092 | Medium | 2023-03-27 | Not applicable | Proof of concept only | The OAuth Single Sign On Free WordPress plugin before 6.24.2, OAuth Single Sign On Standard WordPress plugin before 28.4.9, OAuth Single Sign On Premium WordPress plugin before 38.4.9 and OAuth Single Sign On Enterprise WordPress plugin before 48.4.9 do not have CSRF checks when deleting Identity Providers (IdP), which could allow attackers to make logged in admins delete arbitrary IdP via a CSRF attack |
| CVE-2022-4496 | Medium | 2023-01-30 | Not applicable | No public exploit | The SAML SSO Standard WordPress plugin version 16.0.0 before 16.0.8, SAML SSO Premium WordPress plugin version 12.0.0 before 12.1.0 and SAML SSO Premium Multisite WordPress plugin version 20.0.0 before 20.0.7 does not validate that the redirect parameter to its SSO login endpoint points to an internal site URL, making it vulnerable to an Open Redirect issue when the user is already logged in. |
| CVE-2022-2133 | Medium | 2022-07-17 | Not applicable | No public exploit | The OAuth Single Sign On WordPress plugin before 6.22.6 doesn't validate that OAuth access token requests are legitimate, which allows attackers to log onto the site with the only knowledge of a user's email address. |
| CVE-2020-6850 | Medium | 2020-02-17 | Not applicable | No public exploit | Utilities.php in the miniorange-saml-20-single-sign-on plugin before 4.8.84 for WordPress allows XSS via a crafted SAML XML Response to wp-login.php. This is related to the SAMLResponse and RelayState variables, and the Destination parameter of the samlp:Response XML element. |
| CVE-2019-12346 | Medium | 2019-06-24 | Not applicable | No public exploit | In the miniOrange SAML SP Single Sign On plugin before 4.8.73 for WordPress, the SAML Login Endpoint is vulnerable to XSS via a specially crafted SAMLResponse XML post. |
| CVE-2017-2585 | Medium | 2018-03-12 | No exploit published | No public exploit | Red Hat Keycloak before version 2.5.1 has an implementation of HMAC verification for JWS tokens that uses a method that runs in non-constant time, potentially leaving the application vulnerable to timing attacks. |
| CVE-2016-8629 | Medium | 2018-03-12 | No exploit published | No public exploit | Red Hat Keycloak before version 2.4.0 did not correctly check permissions when handling service account user deletion requests sent to the rest server. An attacker with service account authentication could use this flaw to bypass normal permissions and delete users in a separate realm. |
| CVE-2017-12158 | Medium | 2017-10-26 | No exploit published | No public exploit | It was found that Keycloak would accept a HOST header URL in the admin console and use it to determine web resource locations. An attacker could use this flaw against an authenticated user to attain reflected XSS via a malicious server. |
| CVE-2014-2586 | Medium | 2014-03-24 | Not applicable | Working exploit published | Cross-site scripting (XSS) vulnerability in the login audit form in McAfee Cloud Single Sign On (SSO) allows remote attackers to inject arbitrary web script or HTML via a crafted password. |
| CVE-2014-2536 | Medium | 2014-03-18 | Not applicable | No public exploit | Directory traversal vulnerability in McAfee Cloud Identity Manager 3.0, 3.1, and 3.5.1, McAfee Cloud Single Sign On (MCSSO) before 4.0.1, and Intel Expressway Cloud Access 360-SSO 2.1 and 2.5 allows remote authenticated users to read an unspecified file containing a hash of the administrator password via unknown vectors. |