Fix reflected XSS in echo_jwt and harden JWT handling#7
Open
Montana wants to merge 1 commit into
Open
Conversation
- HTML-escape the reflected token and decoded payload (closes unauthenticated
reflected XSS on all UI-extension routes)
- Pin jwt.decode algorithms=["HS256"] to prevent algorithm confusion
- Use hmac.compare_digest for the X-Perc-App-Secret comparison
- Default app.run to debug=False, opt-in via FLASK_DEBUG
- Use request.path instead of base_url.split("/")[-1]
- Bump python-jose (CVE-2024-33663, CVE-2024-33664) and Flask off the 2019
pins, which also fail to import on Python >= 3.10
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix reflected XSS in
/echo_jwtand harden JWT handlingWhat & why
The
jwtquery parameter is interpolated into the HTML response viastr.format()with no escaping. Since a returned string is served astext/html, any markup in the parameter executes in the browser. Theinvalid-token branch requires no secret, so this is an unauthenticated reflected XSS on all seven UI-extension routes:
Changes
tokenand the decoded payload withmarkupsafe.escape(closes the XSS).jwt.decode(..., algorithms=["HS256"])so the token's ownalgheadercan't select the algorithm (CWE-327 / the CVE-2024-33663 class of bug).
X-Perc-App-Secretheader withhmac.compare_digestinstead of!=(constant-time).app.runtodebug=False, opt-in viaFLASK_DEBUG— the READMEinstructs exposing this via ngrok, and
debug=Trueexposes the Werkzeugdebugger (RCE).
request.pathinstead ofrequest.base_url.split("/")[-1]for thecallback name.
python-jose(CVE-2024-33663, CVE-2024-33664) and Flask off the 2019pins, which also don't import on Python >= 3.10 (
from collections import Mapping).