-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Password bypass vulnerability #12927
Comments
Thanks for the report @a1ien. We are investigating this issue as a priority. |
@a1ien again, thanks for reporting the issue. A PR to fix the shared secret issue has been made.
If the expiration claim is set on the token and it has expired, the parser will return an error here: influxdb/services/httpd/handler.go Lines 1606 to 1608 in 932521b
It ensures an expiration was set here: influxdb/services/httpd/handler.go Lines 1623 to 1627 in 932521b
And is tested here: influxdb/services/httpd/handler_test.go Lines 209 to 219 in 932521b
|
i am not see any check that exp > time.now() |
@a1ien the check isn't done by InfluxDB. It's done by the jwt library InfluxDB uses to parse tokens. The |
@dgnorton Ah you are correct. |
We can authorize by any user. For that we can use jwt token with empty shared_secret.
It's happen because
influxdb/services/httpd/handler.go
Lines 1585 to 1602 in e2af85d
In
Authentication and authorization in InfluxDB
document we not mention anything aboutshared-secret
variable.Also sems like we also not check exp state of token. And once generated token valid forewer.
The text was updated successfully, but these errors were encountered: