Shibboleth Service Provider 2.0

CPE Details

Shibboleth Service Provider 2.0
2.0
2019-11-15 15:28 +00:00
2019-11-15 15:28 +00:00

Alerte pour un CPE

Stay informed of any changes for a specific CPE.
Alert management

CPE Name: cpe:2.3:a:shibboleth:service_provider:2.0:*:*:*:*:*:*:*

Informations

Vendor

shibboleth

Product

service_provider

Version

2.0

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2023-22947 2023-01-10 23:00 +00:00 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."
7.3
HIGH
CVE-2021-28963 2021-03-22 06:02 +00:00 Shibboleth Service Provider before 3.2.1 allows content injection because template generation uses attacker-controlled parameters.
5.3
MEDIUM
CVE-2010-2450 2019-11-07 19:06 +00:00 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.
7.5
HIGH
CVE-2017-16852 2017-11-16 16:00 +00:00 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.
8.1
HIGH
CVE-2015-2684 2015-03-31 12:00 +00:00 Shibboleth Service Provider (SP) before 2.5.4 allows remote authenticated users to cause a denial of service (crash) via a crafted SAML message.
4
Click on the button to the left (OFF), to authorize the inscription of cookie improving the functionalities of the site. Click on the button to the left (Accept all), to unauthorize the inscription of cookie improving the functionalities of the site.