-
Notifications
You must be signed in to change notification settings - Fork 2
fix(security): CodeQL #196 XSS + post-PR #865 dashboard #866
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -709,7 +709,7 @@ services: | |
| supabase-db: | ||
| condition: service_healthy | ||
| ports: | ||
| - ${SUPABASE_REALTIME_PORT:-4000}:4000 | ||
| - ${SUPABASE_REALTIME_PORT:-4010}:4000 | ||
|
Comment on lines
711
to
+712
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🧩 Analysis chain🏁 Script executed: #!/bin/bash
# Verify env files and test defaults for port consistency
echo "=== Checking env.supabase for SUPABASE_REALTIME_PORT ==="
rg -n "SUPABASE_REALTIME_PORT" pmoves/env.supabase pmoves/env.tier-supabase 2>/dev/null || echo "Files not found or no matches"
echo ""
echo "=== Checking test files for hardcoded port 4000 references ==="
rg -n "localhost:4000" pmoves/tests/Repository: POWERFULMOVES/PMOVES.AI Length of output: 460 Update The docker-compose change from port 4000→4010 avoids a port collision, but The internal container port (4000) correctly remains unchanged, so container-to-container references continue working. 🤖 Prompt for AI Agents |
||
| networks: | ||
| - pmoves_api | ||
| - pmoves_data | ||
|
|
||
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.
🧩 Analysis chain
🏁 Script executed:
Repository: POWERFULMOVES/PMOVES.AI
Length of output: 1372
🏁 Script executed:
Repository: POWERFULMOVES/PMOVES.AI
Length of output: 5368
🏁 Script executed:
Repository: POWERFULMOVES/PMOVES.AI
Length of output: 201
🏁 Script executed:
Repository: POWERFULMOVES/PMOVES.AI
Length of output: 2179
🏁 Script executed:
Repository: POWERFULMOVES/PMOVES.AI
Length of output: 488
URL validation missing in popup.js:
chrome.tabs.create()passes unvalidated URLs.At
popup.js:188, the code passesr.urldirectly tochrome.tabs.create({ url: r.url })without validation. This URL originates fromshapeSvgUrl()(pmoves-api.js:319), which constructs it from the configurable_services.gatewaywithout protocol validation:If
_services.gatewayis set to ajavascript:ordata:URL, the extension would attempt to open it, bypassing the protocol validation now applied inoptions.js.Apply the same
new URL()constructor + protocol check before callingchrome.tabs.create()to ensure consistent security posture.🤖 Prompt for AI Agents