BaseFortify

Publication date: 2025-10-22

Last updated on: 2025-10-30

Assigner: GitHub, Inc.

Description

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

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2025-10-22

Last Modified

2025-10-30

Generated

2026-07-06

AI Q&A

2025-10-23

EPSS Evaluated

2026-07-05

NVD

CVE-2025-62710

Affected Vendors & Products

Vendor	Product	Version / Range
sakailms	sakai	to 23.5 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-337	A Pseudo-Random Number Generator (PRNG) is initialized from a predictable seed, such as the process ID or system time.

Attack-Flow Graph

Executive Summary

This vulnerability involves the Sakai Collaboration and Learning Environment using a non-cryptographic pseudo-random number generator (java.util.Random) to initialize an AES256 encryption key (serverSecretKey). Because java.util.Random is predictable from limited seed information, an attacker who obtains ciphertexts and can approximate the seed can reconstruct the encryption key and decrypt protected data.

Impact Analysis

If exploited, this vulnerability allows an attacker to decrypt sensitive data that was protected by the affected encryption service, potentially exposing confidential information stored or exported by Sakai.

Mitigation Strategies

Upgrade Sakai to version 23.5, 25.0, or later where the issue is patched (Sakai versions 23.5 and 25.0 include the fix for this vulnerability).

Hi! I’m here to help you understand CVE-2025-62710. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70