CVE-2014-9970 — jasypt
HIGHCVE-2014-9970 is a high-severity (CVSS 7.5) Information Exposure vulnerability in org.jasypt:jasypt. A fix is available for org.jasypt:jasypt — see the affected versions and patch details below.
Exposure of Sensitive Information to an Unauthorized Actor in Apache Jasypt
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2014-9970 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.jasypt:jasyptReal-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
jasypt before 1.9.2 allows a timing attack against the password hash comparison.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jasypt:jasypt | all versions | 1.9.2org.jasypt:jasypt:1.9.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jasypt:jasypt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jasypt:jasypt to 1.9.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-9970 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2014-9970 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2014-9970. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Data Grid 7.1.2 | see advisory | RHSA-2018:0294 |
| Red Hat JBoss BPMS 6.4 | jasypt | RHSA-2017:2546 |
| Red Hat JBoss BRMS 6.4 | jasypt | RHSA-2017:2547 |
| Red Hat JBoss EAP 7 | see advisory | RHSA-2017:2810 |
| Red Hat JBoss Enterprise Application Platform 7.0 for RHEL 6 | eap7-artemis-native-0:1.1.0-13.redhat_4.ep7.el6 | RHSA-2017:2809 |
| Red Hat JBoss Enterprise Application Platform 7.0 for RHEL 6 | eap7-jboss-ec2-eap-0:7.0.8-1.GA_redhat_1.ep7.el6 | RHSA-2017:2811 |
| Red Hat JBoss Enterprise Application Platform 7.0 for RHEL 7 | eap7-artemis-native-0:1.1.0-13.redhat_4.ep7.el7 | RHSA-2017:2808 |
| Red Hat Single Sign-On 7.1 | see advisory | RHSA-2017:2906 |
Frequently Asked Questions
Is CVE-2014-9970 in your dependencies?
O3 Security finds CVE-2014-9970 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.