Gotify: Insufficiently Protected Password Change endpoint
gotify server
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/gotify/server/v2 Go |
| No fix yet |
| github.com/gotify/server/v3 Go |
|
|
| github.com/gotify/server Go |
gotify server
| Product | Affected | Fixed in |
|---|---|---|
| github.com/gotify/server/v2 Go |
| No fix yet |
| github.com/gotify/server/v3 Go |
|
|
| github.com/gotify/server Go |
|
| No fix yet |
Gotify server is a simple server for sending and receiving messages in real-time per WebSocket. Prior to 3.0.0, the password change endpoint (POST /current/user/password) accepts a valid client token without requiring the account's current password or another elevated authentication step. An attacker who obtains a client token can set a new password for the associated user, taking control of password authentication and forcing account recovery through an administrator or direct database access. This issue is fixed in version 3.0.0.
From the CVE record · GitHub_M
Before 3.0.0, Gotify server’s password change endpoint accepts a valid client token without requiring the current password or another elevated authentication step. An attacker who obtains a client token can set a new password for the associated user, taking control of password authentication and forcing account recovery through an administrator or direct database access.
Operators of Go package github.com/gotify/server/v3 before 3.0.0, github.com/gotify/server/v2 through 2.9.1, or github.com/gotify/server at any version should check their deployments.