Apache Answer: AdminToken not invalidated after admin deactivation
Apache Software Foundation Apache Answer
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/apache/incubator-answer Go |
|
|
| github.com/apache/answer Go |
|
|
Apache Software Foundation Apache Answer
| Product | Affected | Fixed in |
|---|---|---|
| github.com/apache/incubator-answer Go |
|
|
| github.com/apache/answer Go |
|
|
Improper Restriction of Security Token Assignment vulnerability in Apache Answer.
This issue affects Apache Answer: through 2.0.0.
Previously issued administrative tokens were not invalidated after an administrator account was suspended, deleted, or deactivated, allowing continued access to administrative APIs until the token expired. Users are recommended to upgrade to version 2.0.1, which fixes the issue.
From the CVE record · apache
Apache Answer did not invalidate previously issued administrative tokens when an administrator account was suspended, deleted, or deactivated. Someone holding such a token could continue accessing administrative APIs until it expired.
Teams running Apache Answer through 2.0.0 or using the Go packages github.com/apache/incubator-answer or github.com/apache/answer before 2.0.1 should check their deployments.