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.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
Low
Partial data leak
Integrity
High
Complete data modification
Availability
None
No disruption
CVSS Vector v3.1
Weakness Type (CWE)
Vulnerable Products 1
| Configuration | From (including) | Up to (excluding) |
|---|---|---|
|
Miguelgrinberg Flask-Httpauth
cpe:2.3:a:miguelgrinberg:flask-httpauth:*:*:*:*:*:python:*:*
|
— |
4.8.1
|
References 3
https://github.com/miguelgrinberg/Flask-HTTPAuth/releases/tag/v4.8.1
security-advisories@github.com
https://github.com/miguelgrinberg/Flask-HTTPAuth/security/advisories/GHSA-p44q-…
security-advisories@github.com
https://github.com/miguelgrinberg/flask-httpauth/commit/b15ffe9e50e110d7174ccd9…
security-advisories@github.com