Cyber Resilience

CVE-2025-68704

Crypto Weakness in Samrocketman Jervis ≤ 2.2

Crypto Weakness
Published
13 January 2026
Modified
20 January 2026
Patch / advisory
View advisory
CVSS Score v4 8.2
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0024 15th percentile
Risk Priority 33 floored blend · peak EPSS

Summary

CVE-2025-68704 is a high-severity Use of Insufficiently Random Values (CWE-330) vulnerability in Samrocketman Jervis. Its CVSS base score is 8.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Forge Web Credentials (T1606); ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-12 (Cryptographic Key Establishment and Management) and SC-13 (Cryptographic Protection) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-68704 affects Jervis, a library used for Job DSL plugin scripts and shared Jenkins pipeline libraries. In versions prior to 2.2, Jervis relies on java.util.Random(), which is not cryptographically secure, for timing attack mitigation. This flaw, classified under CWE-330 (Use of Insufficiently Random Values), carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), indicating high confidentiality impact with no requirements for privileges or user interaction.

Remote attackers can exploit this vulnerability over the network with low complexity. By leveraging the predictable randomness from java.util.Random(), adversaries may conduct timing attacks to infer sensitive information processed or protected by Jervis in Jenkins environments, potentially disclosing confidential data without impacting integrity or availability.

The vulnerability is addressed in Jervis version 2.2, where the insecure random number generator is replaced. Security practitioners should upgrade to 2.2 or later, as detailed in the GitHub security advisory (GHSA-c9q6-g3hr-8gww) and the fixing commit (c3981ff71de7b0f767dfe7b37a2372cb2a51974a).

OWASP Top 10 for Web (2025)

A04:2025 Cryptographic Failures

EU & UK References

Vulnerability Data

Jervis is a library for Job DSL plugin scripts and shared Jenkins pipeline libraries. Prior to 2.2, Jervis uses java.util.Random() which is not cryptographically secure for timing attack mitigation. This vulnerability is fixed in 2.2.

CWE(s)
CWE-330

Related Threats

MITRE ATT&CK Enterprise Techniques

T1606 Forge Web Credentials Credential Access
Adversaries may forge credential materials that can be used to gain access to web applications or Internet services.
attack.mitre.org →
T1606.001 Web Cookies Credential Access
Adversaries may forge web cookies that can be used to gain access to web applications or Internet services.
attack.mitre.org →
T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
attack.mitre.org →
T1185 Browser Session Hijacking Collection
Adversaries may take advantage of security vulnerabilities and inherent functionality in browser software to change content, modify user-behaviors, and intercept information as part of various browser session hijacking techniques.
attack.mitre.org →
T1558 Steal or Forge Kerberos Tickets Credential Access
Adversaries may attempt to subvert Kerberos authentication by stealing or forging Kerberos tickets to enable [Pass the Ticket](https://attack.
attack.mitre.org →
T1563 Remote Service Session Hijacking Lateral Movement
Adversaries may take control of preexisting sessions with remote services to move laterally in an environment.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-68701Same product: Samrocketman Jervis
CVE-2025-68703Same product: Samrocketman Jervis
CVE-2025-68931Same product: Samrocketman Jervis
CVE-2025-68925Same product: Samrocketman Jervis
CVE-2025-68702Same product: Samrocketman Jervis
CVE-2025-68698Same product: Samrocketman Jervis
CVE-2024-56089Shared CWE-330
CVE-2026-14570Shared CWE-330
CVE-2024-36389Shared CWE-330
CVE-2023-6376Shared CWE-330

Affected Assets

samrocketman
jervis
≤ 2.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 8 hardening rules · 4 OS baselines
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SC-12 Cryptographic Key Establishment and Management good match

SC-12 requires proper cryptographic key establishment and management, which structurally mandates use of sufficient randomness for key generation.

SC-13 Cryptographic Protection partial match

SC-13 requires selection and implementation of approved cryptographic algorithms and methods, which inherently depend on and enforce sufficiently random values.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce use of cryptographically strong RNGs and catch insufficient randomness during design, coding, and testing.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.24 Use of cryptography mostly match
prevents

Cryptographic controls require use of approved, sufficiently random values for keys and nonces.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect weak randomness but does not prescribe the control itself.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC processes include verification steps that can catch insufficient randomness but do not directly specify RNG requirements.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly prohibit use of weak or predictable random number generators.

A.8.5 Secure authentication partial match
degrades

Secure authentication mechanisms depend on unpredictable values (nonces, salts, session tokens) to resist guessing.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (3 rules)
  • V-248563 The OL 8 SSH server must be configured to use strong entropy. prevents CWE-330
  • V-248599 OL 8 must enable the hardware random number generator entropy gatherer service. prevents CWE-330
  • V-248600 OL 8 must have the packages required to use the hardware random number generator entropy gatherer service. prevents CWE-330
Oracle Linux 9 (1 rule)
  • V-271511 OL 9 must enable the hardware random number generator entropy gatherer service. prevents CWE-330
RHEL 8 (3 rules)
  • V-244527 RHEL 8 must have the packages required to use the hardware random number generator entropy gatherer service. prevents CWE-330
  • V-230253 RHEL 8 must ensure the SSH server uses strong entropy. prevents CWE-330
  • V-230285 RHEL 8 must enable the hardware random number generator entropy gatherer service. prevents CWE-330
RHEL 9 (1 rule)
  • V-257782 RHEL 9 must enable the hardware random number generator entropy gatherer service. prevents CWE-330

References