CVE-2024-47876 — sakai-kernel-impl
Fix: sakaiproject/sakai@a9aadd9CVE-2024-47876 is a CWE-285 vulnerability in org.sakaiproject.kernel:sakai-kernel-impl. A fix is available for org.sakaiproject.kernel:sakai-kernel-impl — see the affected versions and patch details below.
Sakai: Kernel users created with type roleview can login as a normal user
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-47876.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
org.sakaiproject.kernel:sakai-kernel-implReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Sakai is a Collaboration and Learning Environment. Starting in version 23.0 and prior to version 23.2, kernel users created with type roleview can log in as a normal user. This can result in illegal access being granted to the system. Version 23.3 fixes this vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.sakaiproject.kernel:sakai-kernel-impl | ≥ 23.0&&< 23.3 | 23.3org.sakaiproject.kernel:sakai-kernel-impl:23.3 |
Affected Products
sakaisakailmsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.sakaiproject.kernel:sakai-kernel-impl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.sakaiproject.kernel:sakai-kernel-impl to 23.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-47876 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2024-47876 in your dependencies?
Find it across Maven, including transitive dependencies.