Jervis's Salt for PBKDF2 derived from password

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2025-68703: 0.13% estimated exploitation activity in the next 30 days; percentile 2.82 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Vulnerability https://github.com/samrocketman/jervis/blob/157d2b63ffa5c4bb1d8ee2254950fd2231de2b05/src/main/groovy/net/gleske/jervis/tools/SecurityIO.groovy#L869-L870 https://github.com/samrocketman/jervis/blob/157d2b63ffa5c4bb1d8ee2254950fd2231de2b05/src/main/groovy/net/gleske/jervis/tools/SecurityIO.groovy#L894-L895 The salt is derived from sha256Sum(passphrase). Two encryption operations with the same password will have the same derived key. Impact Pre-computation attacks. Severity is considered low for internal uses of this library and high for consumers of this library. Patches Jervis will generate a random salt for each password and store it alongside the ciphertext. Upgrade to Jervis 2.2. Workarounds None References - NIST SP 800-132: Password-Based Key Derivation

Published by the source

13 Jan 2026, 14:53 UTC

Last modified by the source

21 Jan 2026, 16:23 UTC

Source last checked

26 Oct 2026, 16:43 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-36h5-vrq6-pp34

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-68703

Advisory: Jervis's Salt for PBKDF2 derived from password
IDs: CVE-2025-68703, GHSA-36h5-vrq6-pp34
Record: https://patchnext.com/advisories/cve-2025-68703 (revision 1, source checked 26 Oct 2026, 16:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: net.gleske:jervis 2.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven net.gleske:jervis: affected < 2.2; fixed in 2.2

## Suggested inspection (read-only)
- Maven net.gleske:jervis: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on net.gleske:jervis.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-36h5-vrq6-pp34 (GitHub-reviewed advisory GHSA-36h5-vrq6-pp34 lists affected ranges: Maven net.gleske:jervis >=0 <2.2)

Commands are suggestions: review each one before running it.