PatchTheCVEnot yet commons ssl vulnerabilities and fixes
Recent CVEs affecting not yet commons ssl, with upgrade or downgrade steps. 1 tracked.
Also searched as: notyetcommonsssl.
not yet commons ssl has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2014-10-25. Highest priority: CVE-2014-3604 (score 39/100).
- CVE-2014-3604 MEDIUM 6.8 UPGRADE Certificates.java in Not Yet Commons SSL before 0.3.15 does not properly verify that the server hostname match
FAQ
How do I fix not yet commons ssl vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is not yet commons ssl being exploited right now?
None of the tracked not yet commons ssl CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which not yet commons ssl CVE should I patch first?
CVE-2014-3604 currently ranks highest (39/100): Certificates.java in Not Yet Commons SSL before 0.3.15 does not properly verify that the server hostname match.