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

Advisory record · `GHSA-cmxj-wx9v-52qr`

- **Identifiers:** `GHSA-cmxj-wx9v-52qr` · `CVE-2014-3604`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-297](https://cwe.mitre.org/data/definitions/297.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 14 May 2022
- **Updated:** 5 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 May 2022, 03:59 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `ca.juliusdavies:not-yet-commons-ssl` (Maven): affected `<0.3.15`; fixed in `0.3.15`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Not Yet Commons SSL versions before 0.3.15 do not properly check that the server hostname matches the Common Name in a certificate's subject. An attacker who can intercept network traffic (a man-in-the-middle position) can present any valid certificate and impersonate the SSL server. Upgrade to version 0.3.15, which is the listed fix.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0094, the 61st percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:12 UTC: First seen by agentprime
- 31 Oct 2026, 15:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-cmxj-wx9v-52qr)

## Sources

- [GitHub Advisory Database: GHSA-cmxj-wx9v-52qr](https://github.com/advisories/GHSA-cmxj-wx9v-52qr)
- [OSV: GHSA-cmxj-wx9v-52qr](https://osv.dev/vulnerability/GHSA-cmxj-wx9v-52qr)
- <https://nvd.nist.gov/vuln/detail/CVE-2014-3604>
- <https://bugzilla.redhat.com/show_bug.cgi?id=1131803>
- <https://exchange.xforce.ibmcloud.com/vulnerabilities/97659>
- <https://github.com/victims/victims-cve-db/blob/master/database/java/2014/3604.yaml>
- <http://juliusdavies.ca/svn/viewvc.cgi/not-yet-commons-ssl?view=rev&revision=172>
- <http://rhn.redhat.com/errata/RHSA-2015-1888.html>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-cmxj-wx9v-52qr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-cmxj-wx9v-52qr/>. Everything for agents: <https://agentprime.io/llms.txt>.
