Sprout Track: Authentication bypass via default JWT signing secret
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Oak-and-Sprout | sprout-track | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Oak-and-sprout | Sprout-track |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.369% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Oak-and-sprout
Oak-and-sprout sprout-track |
|
| Vendors & Products |
Oak-and-sprout
Oak-and-sprout sprout-track |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Sprout Track: Authentication bypass via default JWT signing secret | |
| Weaknesses | CWE-798 | |
| References |
|
|
| Metrics |
cvssV4_0
|