Security: Flask debug mode enabled by default, exposed on 0.0.0.0#445
Open
chinhkrb113 wants to merge 1 commit into666ghj:mainfrom
Open
Conversation
DEBUG defaults to True (FLASK_DEBUG env var is 'True' unless overridden) and the server binds to 0.0.0.0. When debug mode is active, Flask enables the Werkzeug interactive debugger, which allows arbitrary Python code execution via the browser-accessible debugger console if an exception is triggered. Combined with the public bind address this creates a remote code execution vector on any deployment that forgets to set FLASK_DEBUG=False. Affected files: config.py Signed-off-by: ChinhLee <76194645+chinhkrb113@users.noreply.github.com>
dosubot
bot
added
the
size:S
koyouko
added a commit
to koyouko/MiroFish
that referenced
this pull request
Apr 6, 2026
- fix(runner): prevent action data loss from partial line reads (666ghj#460) Track safe_position; only advance past newline-terminated lines to avoid permanent data loss when the writer is mid-flush. - fix(build): restrict Python to <3.13 to avoid tiktoken failure (666ghj#453) tiktoken wheels are not available for Python 3.13+. - fix(security): default FLASK_DEBUG to False (666ghj#445) Debug mode was on by default, exposing the Werkzeug debugger in production deployments on 0.0.0.0. - fix(polling): stop frontend polling when backend fails (666ghj#448) Step2 and Step3 now detect failed status and error-count limits, stopping the polling interval instead of looping indefinitely. - fix(simulation): stop Step2 hanging after prepare failures (666ghj#336) Reset state flags on each prepare run; raise ValueError instead of returning silently so the task manager marks the task as failed. Co-Authored-By: koyouko <koyouko@users.noreply.github.com>
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
1 participant
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.
Description
DEBUG defaults to True (FLASK_DEBUG env var is 'True' unless overridden) and the server binds to 0.0.0.0. When debug mode is active, Flask enables the Werkzeug interactive debugger, which allows arbitrary Python code execution via the browser-accessible debugger console if an exception is triggered. Combined with the public bind address this creates a remote code execution vector on any deployment that forgets to set FLASK_DEBUG=False.
Changes
backend/app/config.py(modified)Type of Change
Testing
Severity:
high