How severe is CVE-2014-9970?

CVE-2014-9970 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2014-9970?

CVE-2014-9970 affects the following packages: org.jasypt:jasypt (Maven). Ecosystems affected: Maven.

How do I fix CVE-2014-9970?

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.

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

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.

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

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

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

No public exploit code has been indexed for CVE-2014-9970 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-9970?

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

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

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

CVE-2014-9970 was published on May 21, 2017 and was last updated on April 10, 2026. 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

HIGH severity

CVE-2014-9970 — jasypt

HIGH

CVE-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

Also known asGHSA-r5c2-rxh2-f5h2

Published

May 21, 2017

Updated

Apr 10, 2026

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 ↗

2.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% 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

1 pkg affected

☕org.jasypt:jasypt

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

jasypt before 1.9.2 allows a timing attack against the password hash comparison.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jasypt:jasypt`	all versions	1.9.2`org.jasypt:jasypt:1.9.2`

Affected Products

1 product · 1 configurations

Application

jasyptjasypt_project

≤ 1.9.1

range

Detection & mitigation playbook

Open-source dependency

Detect
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
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

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 HatModerate

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

jasypt before 1.9.2 allows a timing attack against the password hash comparison.

O3 Security · Impact-Aware SCA

Is CVE-2014-9970 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works