How severe is CVE-2014-3603?

CVE-2014-3603 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2014-3603?

CVE-2014-3603 affects the following packages: edu.internet2.middleware:shibboleth-identityprovider (Maven), org.opensaml:opensaml (Maven). Ecosystems affected: Maven.

How do I fix CVE-2014-3603?

Update edu.internet2.middleware:shibboleth-identityprovider to 2.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3603 is resolved across your whole dependency graph.

How do I detect CVE-2014-3603 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for edu.internet2.middleware:shibboleth-identityprovider, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2014-3603 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2014-3603 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2014-3603, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2014-3603?

CVE-2014-3603 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 58th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2014-3603?

CVE-2014-3603 is classified as CWE-297 (CWE-297). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-3603 published, and has it been updated?

CVE-2014-3603 was published on May 14, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2014-3603 — shibboleth-identityprovid…

MEDIUM

CVE-2014-3603 is a medium-severity (CVSS 5.9) CWE-297 vulnerability in edu.internet2.middleware:shibboleth-identityprovider. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for edu.internet2.middleware:shibboleth-identityprovider — see the affected versions and patch details below.

Improper Validation of Certificate with Host Mismatch in Shibboleth Identity Provider and OpenSAML Java

Published

May 14, 2022

Updated

Nov 8, 2023

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs58th percentile — riskier than 58% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕edu.internet2.middleware:shibboleth-identityprovider☕org.opensaml:opensaml

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`edu.internet2.middleware:shibboleth-identityprovider`	all versions	2.4.1`edu.internet2.middleware:shibboleth-identityprovider:2.4.1`
☕Maven	`org.opensaml:opensaml`	all versions	2.6.2`org.opensaml:opensaml:2.6.2`

Affected Products

2 products · 2 configurations

Application

identity providershibboleth

< 2.4.1

range

Application

opensaml javashibboleth

< 2.6.2

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The (1) HttpResource and (2) FileBackedHttpResource implementations in S…

bugzilla.redhat.comNVDApr 2019

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for edu.internet2.middleware:shibboleth-identityprovider, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update edu.internet2.middleware:shibboleth-identityprovider to 2.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3603 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-3603 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.9/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

CWE Classification

CWE-297CWE-297

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

First exploit

Apr 8, 2019

Disclosed

May 14, 2022

Last updated

Nov 8, 2023

Identifiers

CVE-2014-3603

References

Advisorynvd.nist.gov · CVE 2014 3603 Webbugzilla.redhat.com · show bug.cgi Webshibboleth.net · secadv 20140813.txt

Related vulnerabilities

Also affects shibboleth-identityprovider

This CVE is medium severity, in line with the other 2 CVEs affecting shibboleth-identityprovider.

CVE-2015-1796CVE-2014-3607

Also affects opensaml

This CVE is medium severity, in line with the other 2 CVEs affecting opensaml.

CVE-2011-1411CVE-2013-6440

Same weakness: CWE-297

This CVE is medium severity; 4 of 4 other CVEs with CWE-297 are rated as high or higher (top: critical).

GHSA-5wf9-h793-w73cCVE-2026-63374CVE-2026-66053CVE-2026-15925Browse all CWE-297

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedNov 8, 2023

CVE-2014-3603 — shibboleth-identityprovid…

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2014-3603 in your dependencies?