How severe is CVE-2014-3604?

No CVSS score has been assigned to CVE-2014-3604 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-3604?

CVE-2014-3604 affects the following packages: ca.juliusdavies:not-yet-commons-ssl (Maven). Ecosystems affected: Maven.

How do I fix CVE-2014-3604?

Update ca.juliusdavies:not-yet-commons-ssl to 0.3.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3604 is resolved across your whole dependency graph.

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

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ca.juliusdavies:not-yet-commons-ssl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2014-3604 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-3604 actively exploited in the wild?

No public exploit code has been indexed for CVE-2014-3604 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

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

CVE-2014-3604 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 61th 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-3604?

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

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

CVE-2014-3604 was published on May 14, 2022 and was last updated on December 5, 2024. 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

CVE-2014-3604 — not-yet-commons-ssl

CVE-2014-3604 is a CWE-310 vulnerability in ca.juliusdavies:not-yet-commons-ssl. A fix is available for ca.juliusdavies:not-yet-commons-ssl — see the affected versions and patch details below.

Improper Validation of Certificate with Host Mismatch in Not Yet Commons SSL

Published

May 14, 2022

Updated

Dec 5, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs61th percentile — riskier than 61% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕ca.juliusdavies:not-yet-commons-ssl

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

Certificates.java in Not Yet Commons SSL before 0.3.15 does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`ca.juliusdavies:not-yet-commons-ssl`	all versions	0.3.15`ca.juliusdavies:not-yet-commons-ssl:0.3.15`

Affected Products

1 product · 1 configurations

Application

not yet commons sslnot_yet_commons_ssl_project

≤ 0.3.14

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ca.juliusdavies:not-yet-commons-ssl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ca.juliusdavies:not-yet-commons-ssl to 0.3.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3604 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Red Hat JBoss SOA Platform 4 is now in Phase 3, Extended Life Support, of its life cycle. This issue has been rated as having Important security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network…

Product	Fixed in	Advisory
Red Hat JBoss SOA Platform 5.3	`commons-ssl`	RHSA-2015:1888

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-3604 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works