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.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Privileges Required
High
Admin privileges needed
User Interaction
Required
User action required
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
High
Complete data modification
Availability
None
No disruption
CVSS Vector v3.1
Weakness Type (CWE)
References 4
https://github.com/Erudika/scoold/commit/de018c17a60c352f318109a762a377c325a5fd…
security-advisories@github.com
https://github.com/Erudika/scoold/commit/e527d4da1ac04b6a35bd86e560c279f0160c5c…
security-advisories@github.com
https://github.com/Erudika/scoold/releases/tag/1.69.1
security-advisories@github.com
https://github.com/Erudika/scoold/security/advisories/GHSA-6q9q-cqq5-hvmq
security-advisories@github.com