Sprout Trackに認証回避の脆弱性、1.3.5で修正
Summary
Sprout Trackの1.3.5より前の版には、JWT_SECRETを未設定のまま運用していると、認証なしで管理者になりすませる脆弱性があります。自前でホストしている組織は、1.3.5以降へ更新し、JWT_SECRETの設定を確認してください。
AI summary
Produced by SecPulse using an external AI model; it may contain mistakes. Check the original description and references below before acting on it.
Sprout Trackの1.3.5より前の版には、JWT_SECRETを未設定のまま運用していると、認証なしで管理者になりすませる脆弱性があります。自前でホストしている組織は、1.3.5以降へ更新し、JWT_SECRETの設定を確認してください。
Original description The description as published by the source.
Sprout Track is a self-hosted baby tracking application. Prior to 1.3.5, Sprout Track uses a publicly known hardcoded signing secret when JWT_SECRET is unset, and standard setup does not generate a unique secret. On a network-reachable affected deployment, an unauthenticated attacker can sign JWTs with arbitrary claims, including system-administrator claims, to access administrative functionality and read or modify family, child activity, account, and email data. Deployments with a strong unique JWT_SECRET are not affected. Managed and hosted instances were reported remediated. This issue is fixed in version 1.3.5.
Source: CVE.org (CVE Program・cvelistV5) NVD GitHub Advisory
References
- advisory github.com
- advisory nvd.nist.gov
- web security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com