CVE-2025-68703: Jervis Package Vulnerability Due to Predictable Salt in PBKDF2
Summary
CVE-2025-68703: Jervis's Salt for PBKDF2 derived from password. Affects net.gleske:jervis versions < 2.2. Fixed in 2.2. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
Jervis is a tool designed for continuous integration and deployment, primarily used in the Java ecosystem. It facilitates automation tasks and enhances security through password-based key derivation. However, a vulnerability has been identified in its implementation of PBKDF2, where the salt used for key derivation is derived from the SHA-256 hash of the passphrase, leading to predictable outputs.
Vulnerability Detail
The vulnerability arises from the method used to derive the salt for PBKDF2 encryption. Specifically, the salt is generated using the SHA-256 hash of the user's passphrase. This means that if two users use the same password, they will end up with the same derived key, making the system susceptible to pre-computation attacks. Attackers can exploit this predictability to crack passwords more easily, especially in scenarios where the same password is reused across different accounts.
How To Fix
Latest published version: 2.4 as of 22 Oct 2026
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
2.2
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There are no effective workarounds available for this vulnerability. The only recommended action is to upgrade to the patched version of Jervis.
Conclusion
The vulnerability CVE-2025-68703 in the Jervis package poses a significant risk due to the predictable salt used in PBKDF2 key derivation. Users are strongly advised to upgrade to version 2.2 or later to ensure their applications are secure against potential pre-computation attacks.
See every vulnerability recorded for net.gleske:jervis →
FAQ
The vulnerability is related to the predictable salt used in PBKDF2 key derivation, which can lead to pre-computation attacks.
The vulnerability has a CVSS score of 8.7, indicating a high severity level, particularly for consumers of the library.
You should upgrade to Jervis version 2.2 or later to mitigate the vulnerability.
No, there are no workarounds available. The only solution is to upgrade to the patched version.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application using the Vulert playground without any signup.
References
Related vulnerabilities
Recent vulnerabilities recorded for net.gleske:jervis.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
