GHSA-hh7m-rx4f-4vpv

Suggest an improvement
Source
https://github.com/advisories/GHSA-hh7m-rx4f-4vpv
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2021/01/GHSA-hh7m-rx4f-4vpv/GHSA-hh7m-rx4f-4vpv.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-hh7m-rx4f-4vpv
Aliases
Published
2021-01-11T20:38:28Z
Modified
2024-09-20T18:00:57.406812Z
Severity
  • 7.4 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N CVSS Calculator
  • 8.3 (High) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N CVSS Calculator
Summary
CSRF can expose users authentication token
Details

Issue

The /login and /change endpoints can return the authenticated user's authentication token in response to a GET request. Since GET requests aren't protected with a CSRF token, this could lead to a malicious 3rd party site acquiring the authentication token.

Patches

Version 3.4.5 and soon to be released 4.0.0 are patched.

Workarounds

If you aren't using authentication tokens - you can set the SECURITYTOKENMAX_AGE to "0" (seconds) which should make the token unusable.

References

None

References

Affected packages

PyPI / flask-security-too

Package

Name
flask-security-too
View open source insights on deps.dev
Purl
pkg:pypi/flask-security-too

Affected ranges

Type
ECOSYSTEM
Events
Introduced
3.3.0
Fixed
3.4.5

Affected versions

3.*

3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
3.4.1
3.4.2
3.4.3
3.4.4