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 editing custom url not changing default url for default provider,… #156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
fix editing custom url not changing default url for default provider,… #156
Changes from all commits
05cd0beFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
Exception details leaked to API response.
str(e)is embedded directly into the client-facingmessagefield. Static analysis (CodeQL) flags this as information exposure through an exception — internal paths or implementation details fromrmtree/filesystem errors could leak to the client. Log the full exception server-side (already done vialogger.error) and return a generic message to the caller.🔒️ Proposed fix
except Exception as e: logger.error(f"Error clearing login data: {e}") return JSONResponse( status_code=500, content={ "success": False, - "message": f"Error clearing login data: {str(e)}", + "message": "Error clearing login data. Please check the server logs for details.", }, )Note: this same pattern (raw
str(e)returned to the client) recurs in the other exception handlers in this file (e.g.get_settings,get_ai_keys,save_ai_key,set_default_provider); consider fixing consistently across the file.📝 Committable suggestion
🧰 Tools
🪛 GitHub Check: CodeQL
[warning] 110-113: Information exposure through an exception
Stack trace information flows to this location and may be exposed to an external user.
🪛 Ruff (0.15.20)
[warning] 105-105: Do not catch blind exception:
Exception(BLE001)
[warning] 112-112: Use explicit conversion flag
Replace with conversion flag
(RUF010)
🤖 Prompt for AI Agents
Source: Linters/SAST tools
Uh oh!
There was an error while loading. Please reload this page.