CVE-2025-62710
Unknown Unknown - Not Provided
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-05-07
AI Q&A
2025-10-23
EPSS Evaluated
2026-05-05
NVD
CVE-2025-62710
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
sakailms sakai to 23.5 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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
AI Powered Q&A
Can you explain this vulnerability to me?

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.


How can this vulnerability impact me? :

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.


What immediate steps should I take to mitigate this vulnerability?

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


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart