fix: remove unsafe eval() in evals.py#594
Open
orbisai0security wants to merge 1 commit intoabi:mainfrom
Open
Conversation
Automated security fix generated by Orbis Security AI
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.
Summary
Fix critical severity security issue in
backend/routes/evals.py.Vulnerability
V-004backend/routes/evals.py:36Description: No authentication controls are present on any of the 11 discovered API endpoints. All endpoints are fully accessible to unauthenticated users on the network. This allows any attacker to trigger expensive AI model evaluations, read all stored evaluation data, abuse the screenshot endpoint for SSRF attacks, and perform all backend operations without any identity verification.
Changes
backend/config.pybackend/routes/evals.pyVerification
Automated security fix by OrbisAI Security