Overview 18 matches · 3 in Waratek scope · 1 protected · 1 exploited · 0 CISA KEV · 2 public PoC · 0 EPSS ≥ 0.5
18matches
3in Waratek scope16.7%
1protected5.6%
1exploited5.6%
0CISA KEV0.0%
2public PoC11.1%
0EPSS ≥ 0.50.0%
Protected by Waratek
1
5.6%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
2
11.1%
Outside Waratek scope
0
0.0%
Not applicable
15
83.3%
Withdrawn CVE
0
0.0%
blocked by ARMR today
1
5.6%
partly blocked
0
0.0%
not blocked
17
94.4%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 3 / year
20112
Not applicable2
Medium2
not blocked2
No public exploit2
20120
20130
20141
Protected by Waratek1
Medium1
blocked by ARMR today1
No public exploit1
20152
No exploit published1
Not applicable1
Medium2
not blocked2
No public exploit2
20160
20172
Not applicable2
High2
not blocked2
No public exploit2
20182
Not applicable2
Medium2
not blocked2
No public exploit2
20193
No exploit published1
Not applicable2
High2
Medium1
not blocked3
No public exploit3
20201
Not applicable1
High1
not blocked1
No public exploit1
20212
Not applicable2
High1
Medium1
not blocked2
No public exploit2
20221
Not applicable1
High1
not blocked1
Working exploit published1
20232
Not applicable2
High2
not blocked2
Exploited1
Proof of concept only1
2011201320152017201920212023
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2023-36661 | High | 2023-06-25 | Not applicable | Exploited | Shibboleth XMLTooling before 3.2.4, as used in OpenSAML and Shibboleth Service Provider, allows SSRF via a crafted KeyInfo element. (This is fixed in, for example, Shibboleth Service Provider 3.4.1.3 on Windows.) |
| CVE-2023-22947 | High | 2023-01-11 | Not applicable | Proof of concept only | Insecure folder permissions in the Windows installation path of Shibboleth Service Provider (SP) before 3.4.1 allow an unprivileged local attacker to escalate privileges to SYSTEM via DLL planting in the service executable's folder. This occurs because the installation goes under C:\opt (rather than C:\Program Files) by default. NOTE: the vendor disputes the significance of this report, stating that "We consider the ACLs a best effort thing" and "it was a documentation mistake." |
| CVE-2022-24129 | High | 2022-02-04 | Not applicable | Working exploit published | The OIDC OP plugin before 3.0.4 for Shibboleth Identity Provider allows server-side request forgery (SSRF) due to insufficient restriction of the request_uri parameter. This allows attackers to interact with arbitrary third-party HTTP services. |
| CVE-2021-31826 | High | 2021-04-27 | Not applicable | No public exploit | Shibboleth Service Provider 3.x before 3.2.2 is prone to a NULL pointer dereference flaw involving the session recovery feature. The flaw is exploitable (for a daemon crash) on systems not using this feature if a crafted cookie is supplied. |
| CVE-2021-28963 | Medium | 2021-03-22 | Not applicable | No public exploit | Shibboleth Service Provider before 3.2.1 allows content injection because template generation uses attacker-controlled parameters. |
| CVE-2020-27978 | High | 2020-10-28 | Not applicable | No public exploit | Shibboleth Identify Provider 3.x before 3.4.6 has a denial of service flaw. A remote unauthenticated attacker can cause a login flow to trigger Java heap exhaustion due to the creation of objects in the Java Servlet container session. |
| CVE-2019-19191 | High | 2019-11-21 | Not applicable | No public exploit | Shibboleth Service Provider (SP) 3.x before 3.1.0 shipped a spec file that calls chown on files in a directory controlled by the service user (the shibd account) after installation. This allows the user to escalate to root by pointing symlinks to files such as /etc/shadow. |
| CVE-2010-2450 | High | 2019-11-07 | Not applicable | No public exploit | The keygen.sh script in Shibboleth SP 2.0 (located in /usr/local/etc/shibboleth by default) uses OpenSSL to create a DES private key which is placed in sp-key.pm. It relies on the root umask (default 22) instead of chmoding the resulting file itself, so the generated private key is world readable by default. |
| CVE-2014-3603 | Medium | 2019-04-04 | No exploit published | No public exploit | The (1) HttpResource and (2) FileBackedHttpResource implementations in Shibboleth Identity Provider (IdP) before 2.4.1 and OpenSAML Java 2.6.2 do not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate. |
| CVE-2018-0489 | Medium | 2018-02-27 | Not applicable | No public exploit | Shibboleth XMLTooling-C before 1.6.4, as used in Shibboleth Service Provider before 2.6.1.4 on Windows and other products, mishandles digital signatures of user data, which allows remote attackers to obtain sensitive information or conduct impersonation attacks via crafted XML data. NOTE: this issue exists because of an incomplete fix for CVE-2018-0486. |
| CVE-2018-0486 | Medium | 2018-01-13 | Not applicable | No public exploit | Shibboleth XMLTooling-C before 1.6.3, as used in Shibboleth Service Provider before 2.6.0 on Windows and other products, mishandles digital signatures of user attribute data, which allows remote attackers to obtain sensitive information or conduct impersonation attacks via a crafted DTD. |
| CVE-2017-16853 | High | 2017-11-16 | Not applicable | No public exploit | The DynamicMetadataProvider class in saml/saml2/metadata/impl/DynamicMetadataProvider.cpp in OpenSAML-C in OpenSAML before 2.6.1 fails to properly configure itself with the MetadataFilter plugins and does not perform critical security checks such as signature verification, enforcement of validity periods, and other checks specific to deployments, aka CPPOST-105. |
| CVE-2017-16852 | High | 2017-11-16 | Not applicable | No public exploit | shibsp/metadata/DynamicMetadataProvider.cpp in the Dynamic MetadataProvider plugin in Shibboleth Service Provider before 2.6.1 fails to properly configure itself with the MetadataFilter plugins and does not perform critical security checks such as signature verification, enforcement of validity periods, and other checks specific to deployments, aka SSPCPP-763. |
| CVE-2015-1796 | Medium | 2015-07-08 | No exploit published | No public exploit | The PKIX trust engines in Shibboleth Identity Provider before 2.4.4 and OpenSAML Java (OpenSAML-J) before 2.6.5 trust candidate X.509 credentials when no trusted names are available for the entityID, which allows remote attackers to impersonate an entity via a certificate issued by a shibmd:KeyAuthority trust anchor. |
| CVE-2015-2684 | Medium | 2015-03-31 | Not applicable | No public exploit | Shibboleth Service Provider (SP) before 2.5.4 allows remote authenticated users to cause a denial of service (crash) via a crafted SAML message. |
| CVE-2013-6440 | Medium | 2014-02-14 | Protected by Waratek | No public exploit | The (1) BasicParserPool, (2) StaticBasicParserPool, (3) XML Decrypter, and (4) SAML Decrypter in Shibboleth OpenSAML-Java before 2.6.1 set the expandEntityReferences property to true, which allows remote attackers to conduct XML external entity (XXE) attacks via a crafted XML DOCTYPE declaration. |
| CVE-2011-1411 | Medium | 2011-09-02 | Not applicable | No public exploit | Shibboleth OpenSAML library 2.4.x before 2.4.3 and 2.5.x before 2.5.1, and IdP before 2.3.2, allows remote attackers to forge messages and bypass authentication via an "XML Signature wrapping attack." |
| CVE-2011-2516 | Medium | 2011-07-11 | Not applicable | No public exploit | Off-by-one error in the XML signature feature in Apache XML Security for C++ 1.6.0, as used in Shibboleth before 2.4.3 and possibly other products, allows remote attackers to cause a denial of service (crash) via a signature using a large RSA key, which triggers a buffer overflow. |