Cyber Resilience

CVE-2025-62710

Sakailms Sakai ≤ 23.5

Published
22 October 2025
Modified
30 October 2025
Patch / advisory
View advisory
CVSS Score v3.1 5.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0019 8th percentile
Risk Priority 44 floored blend · peak EPSS

Summary

CVE-2025-62710 is a medium-severity PRNG (CWE-337) vulnerability in Sakailms Sakai. Its CVSS base score is 5.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Weaken Encryption (T1600); ranked at the 8th 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 SA-11 (Developer Testing and Evaluation) and SC-12 (Cryptographic Key Establishment and Management) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A04:2025 Cryptographic Failures

EU & UK References

Vulnerability Data

Sakai is a Collaboration and Learning Environment. Prior to versions 23.5 and 25.0, EncryptionUtilityServiceImpl initialized an AES256TextEncryptor password (serverSecretKey) using RandomStringUtils with the default java.util.Random. java.util.Random is a non‑cryptographic PRNG and can be predicted from limited state/seed information (e.g., start…

more

time window), substantially reducing the effective search space of the generated key. An attacker who can obtain ciphertexts (e.g., exported or at‑rest strings protected by this service) and approximate the PRNG seed can feasibly reconstruct the serverSecretKey and decrypt affected data. SAK-49866 is patched in Sakai 23.5, 25.0, and trunk.

CWE(s)
CWE-337

Related Threats

MITRE ATT&CK Enterprise Techniques

T1600 Weaken Encryption Defense Impairment
Adversaries may compromise a network device’s encryption capability in order to bypass encryption that would otherwise protect data communications.
attack.mitre.org →
T1600.001 Reduce Key Space Defense Impairment
Adversaries may reduce the level of effort required to decrypt data transmitted over the network by reducing the cipher strength of encrypted communications.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-47876Same product: Sakailms Sakai
CVE-2026-33402Same product: Sakailms Sakai
CVE-2025-7770Shared CWE-337
CVE-2025-20613Shared CWE-337
CVE-2025-55069Shared CWE-337
CVE-2026-25235Shared CWE-337
CVE-2024-22194Shared CWE-337
CVE-2023-49343Shared CWE-337
CVE-2026-26018Shared CWE-337
CVE-2024-7558Shared CWE-337

Affected Assets

sakailms
sakai
≤ 23.5

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 3 hardening rules · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)
  • V6.5.3
  • V7.2.3
  • V11.5.1

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover use of predictable seeds such as time or PID.

SC-12 Cryptographic Key Establishment and Management good match

Proper cryptographic key establishment and management includes using unpredictable seeds for PRNGs that feed key generation.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can require cryptographically secure PRNGs seeded from high-entropy sources.

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 require cryptographically secure PRNG seeding, preventing predictable seeds while the control addresses many additional weaknesses.

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.29 Security testing in development and acceptance mostly match
finds

Security testing can detect and prevent use of weak or predictable PRNG seeds.

A.8.24 Use of cryptography partial match
prevents

Mandates use of cryptography, which includes selecting and seeding PRNGs with sufficient entropy.

A.8.25 Secure development life cycle partial match
prevents

Requires secure development practices that should include proper PRNG seeding.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify cryptographic controls that mitigate predictable seeds.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include choosing cryptographically strong random number generation.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid predictable PRNG seeds.

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-337
  • V-248600 OL 8 must have the packages required to use the hardware random number generator entropy gatherer service. prevents CWE-337
  • V-248599 OL 8 must enable the hardware random number generator entropy gatherer service. prevents CWE-337

References