mirror of
https://github.com/TecharoHQ/anubis.git
synced 2025-10-04 05:41:59 +08:00
6e4e471792* fix(lib): ensure issued challenges don't get double-spent Closes #1002 TL;DR: challenge IDs were not validated at time of token issuance. A dedicated attacker could solve a challenge once and reuse it across multiple sessons in order to mint additional tokens. With the advent of store based challenge issuance in #749, this means that these challenge IDs are only good for 30 minutes. Websites using the most recent version of Anubis have limited exposure to this problem. Websites using older versions of Anubis have a much more increased exposure to this problem and are encouraged to keep this software updated as often and as frequently as possible. * docs: update CHANGELOG Signed-off-by: Xe Iaso <me@xeiaso.net> --------- Signed-off-by: Xe Iaso <me@xeiaso.net>
13 lines
649 B
Go
13 lines
649 B
Go
package challenge
|
|
|
|
import "time"
|
|
|
|
// Challenge is the metadata about a single challenge issuance.
|
|
type Challenge struct {
|
|
ID string `json:"id"` // UUID identifying the challenge
|
|
Method string `json:"method"` // Challenge method
|
|
RandomData string `json:"randomData"` // The random data the client processes
|
|
IssuedAt time.Time `json:"issuedAt"` // When the challenge was issued
|
|
Metadata map[string]string `json:"metadata"` // Challenge metadata such as IP address and user agent
|
|
Spent bool `json:"spent"` // Has the challenge already been solved?
|
|
}
|