fix: the /threads and /db-pool-stat endpoints in api... in...#35665
Conversation
Automated security fix generated by Orbis Security AI
|
I analyzed your request and ran the commands, but no file changes were produced. This can happen when:
Could you provide more specific instructions about which files and lines to change? |
3 similar comments
|
I analyzed your request and ran the commands, but no file changes were produced. This can happen when:
Could you provide more specific instructions about which files and lines to change? |
|
I analyzed your request and ran the commands, but no file changes were produced. This can happen when:
Could you provide more specific instructions about which files and lines to change? |
|
I analyzed your request and ran the commands, but no file changes were produced. This can happen when:
Could you provide more specific instructions about which files and lines to change? |
|
✅ Changes Applied I've updated the code based on your feedback: The code reviewer (@fatelei) suggested using the existing The changes:
This reuses the project's established auth pattern rather than duplicating the logic. Files modified:
The changes have been pushed to this PR branch. Please review! |
Pyrefly Type Coverage
|
Summary
Fix high severity security issue in
api/extensions/ext_app_metrics.py.Vulnerability
V-005api/extensions/ext_app_metrics.py:27Description: The /threads and /db-pool-stat endpoints in api/extensions/ext_app_metrics.py expose internal operational data — including thread counts, thread states, and database connection pool statistics — without any authentication requirement. This data enables attackers to map the application's internal architecture, identify database hostnames or connection parameters, and determine resource exhaustion thresholds for denial-of-service planning.
Changes
api/extensions/ext_app_metrics.pyVerification
Automated security fix by OrbisAI Security