{"answers":{"affected":"2 open source packages ship an affected version, including org.sakaiproject.kernel:sakai-kernel-impl. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-62710 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-62710 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-62710 is a medium-severity vulnerability in sakaiproject sakai, published on 22 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-62710 and fix it if it is affected.\n\nWhat it is: CVE-2025-62710 is a medium-severity vulnerability in sakaiproject sakai, published on 22 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-62710 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.sakaiproject.kernel:sakai-kernel-impl (Maven): affected all versions up to 23.3; no fix listed\n- org.sakaiproject.kernel:sakai-kernel-impl (Maven): affected all versions up to 23.3; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-62710/ (Markdown: https://insights.sbomify.com/CVE-2025-62710/index.md)","id":"CVE-2025-62710","markdown":"https://insights.sbomify.com/CVE-2025-62710/index.md","name":"CVE-2025-62710","record":{"aliases":["GHSA-gr7h-xw4f-wh86"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Sakai LMS","requires_auth":"none","summary":"Attackers can predict server encryption keys due to weak PRNG usage, allowing decryption of protected data in Sakai LMS.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"sakai","vendor":"sakailms"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-337","name":"Predictable Seed in Pseudo-Random Number Generator (PRNG)"}],"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Sakai kernel-impl: predictable PRNG used to generate server‑side encryption key in EncryptionUtilityServiceImpl","id":"CVE-2025-62710","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"Wasmtime vulnerable to segfault when using component resources","id":"CVE-2025-62711"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["23.3"],"package":"org.sakaiproject.kernel:sakai-kernel-impl","purl":null,"source":"GHSA-gr7h-xw4f-wh86"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["23.3"],"package":"org.sakaiproject.kernel:sakai-kernel-impl","purl":"pkg:maven/org.sakaiproject.kernel/sakai-kernel-impl","source":"GHSA-gr7h-xw4f-wh86"}],"prev":{"headline":"ClipBucket v5 is vulnerable to password reset link manipulation","id":"CVE-2025-62709"},"products":["sakai"],"published":"2025-10-22","related":[{"cvss_score":8.7,"headline":"Sakai: Kernel users created with type roleview can login as a normal user","id":"CVE-2024-47876","kev_date_added":null,"published":"2024-10-15"},{"cvss_score":6.1,"headline":"Cross-site scripting in Sakai","id":"CVE-2019-16148","kev_date_added":null,"published":"2019-09-09"},{"cvss_score":1.3,"headline":"SAK-52311: Sakai site-manage group titles can contain XSS content","id":"CVE-2026-33402","kev_date_added":null,"published":"2026-03-26"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-24","vendors":["sakaiproject"]},"summary":"Attackers can predict server encryption keys due to weak PRNG usage, allowing decryption of protected data in Sakai LMS.","url":"https://insights.sbomify.com/CVE-2025-62710/"}