CVE-2014-3603: Improper Validation of Certificate with Host Mismatch in Shibboleth Identity Provider and OpenSAML Java

Quick answers

Is CVE-2014-3603 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2014-3603 being exploited in the wild.

How severe is CVE-2014-3603?

Low severity, with a CVSS score of 3, published 14 May 2022.

Which products and versions are affected?

edu.internet2.middleware:shibboleth-identityprovider (Maven) ECOSYSTEM:introduced=0,fixed=2.4.1; org.opensaml:opensaml (Maven) ECOSYSTEM:introduced=0,fixed=2.6.2.

Is there a fix for CVE-2014-3603?

Yes. edu.internet2.middleware:shibboleth-identityprovider (Maven): upgrade to 2.4.1 or later; org.opensaml:opensaml (Maven): upgrade to 2.6.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2014-3603?

Check whether you run edu.internet2.middleware:shibboleth-identityprovider (Maven) or org.opensaml:opensaml (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

• edu.internet2.middleware:shibboleth-identityprovider (Maven): upgrade to 2.4.1 or later

  # set edu.internet2.middleware:shibboleth-identityprovider to 2.4.1 in your pom.xml or build.gradle

• org.opensaml:opensaml (Maven): upgrade to 2.6.2 or later

  # set org.opensaml:opensaml to 2.6.2 in your pom.xml or build.gradle

Affected products

• edu.internet2.middleware:shibboleth-identityprovider (Maven) ECOSYSTEM:introduced=0,fixed=2.4.1
• org.opensaml:opensaml (Maven) ECOSYSTEM:introduced=0,fixed=2.6.2

Identifiers

• CVE-2014-3603
• GHSA-rm7v-gqfg-p2wc