6.5 MEDIUM
- CVSS version: 3.1
- Attack vector (AV): NETWORK
- Attack complexity (AC): HIGH
- Privileges required (PR): NONE
- User interaction (UI): NONE
- Scope (S): UNCHANGED
- Confidentiality impact (C): LOW
- Integrity impact (I): HIGH
- Availability impact (A): NONE
by @LeSuisse Activity log
- Created automatic suggestion
- @LeSuisse accepted
- @LeSuisse published on GitHub
Flask-HTTPAuth invokes token verification callback when missing or empty token was given by client
Flask-HTTPAuth provides Basic, Digest and Token HTTP authentication for Flask routes. Prior to version 4.8.1, in a situation where the client makes a request to a token protected resource without passing a token, or passing an empty token, Flask-HTTPAuth would invoke the application's token verification callback function with the token argument set to an empty string. If the application had any users in its database with an empty string set as their token, then it could potentially authenticate the client request against any of those users. This issue has been patched in version 4.8.1.
References
-
https://github.com/miguelgrinberg/Flask-HTTPAuth/releases/tag/v4.8.1 x_refsource_MISC
Affected products
- ==< 4.8.1
Matching in nixpkgs
pkgs.python312Packages.flask-httpauth
Extension that provides HTTP authentication for Flask routes
pkgs.python313Packages.flask-httpauth
Extension that provides HTTP authentication for Flask routes
pkgs.python314Packages.flask-httpauth
Extension that provides HTTP authentication for Flask routes
Package maintainers
-
@oxzi Alvar Penning <post@0x21.biz>