Scoold: Forged JWT Accepted as Admin API Token Allowing Unauthorized Access to Sensitive Configuration and Logs
What fixes it
- 1.69.1scooldGitHub
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
Description
Scoold is a Q&A and a knowledge sharing platform for teams. Prior to 1.69.1, checkApiAuth() in src/main/java/com/erudika/scoold/utils/ScooldUtils.java accepts a JWT signed with app_secret_key or para_secret_key for /api/config and /api/stats without requiring a registered API-key jti, and maps the request to the hardcoded administrative API_USER. The special endpoint checks run even when scoold.api_enabled is false. An attacker who obtains either signing secret can forge a token that reads sensitive configuration and server logs and reaches privileged configuration functionality, while an ordinary login-session token is not sufficient. This issue is fixed in version 1.69.1.
Text from CVE List
Affected versions 2
- scooldaffected: < 1.69.1CVE List
- scoold1.66.2GitHub
References 4
- github.com/Erudika/scoold/commit/de018c17a60c352f318109a762a377c325a5fd97Fixvia CVE List
- github.com/Erudika/scoold/commit/e527d4da1ac04b6a35bd86e560c279f0160c5c02Fixvia CVE List
- github.com/Erudika/scoold/releases/tag/1.69.1Fixvia CVE List
- github.com/Erudika/scoold/security/advisories/GHSA-6q9q-cqq5-hvmqAdvisoryvia CVE List