-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
FileUpload Base64 extension fix #11203
Conversation
DryRun Security SummaryThe pull request includes various improvements and enhancements to the Dojo application, focusing on serializers, JSON parser, and file upload functionality, with a strong emphasis on security practices such as file extension validation and careful handling of security-sensitive operations. Expand for full summarySummary: The code changes in this pull request cover various improvements and enhancements to the Dojo application, with a focus on the serializers, JSON parser, and file upload functionality. The key changes include:
Overall, these code changes appear to be focused on improving the functionality and security of the Dojo application, particularly in the areas of file upload handling and JSON data parsing. As an application security engineer, I would recommend thoroughly reviewing the implementation of these features to ensure that they are secure and do not introduce any vulnerabilities. Files Changed:
Code AnalysisWe ran Riskiness🟢 Risk threshold not exceeded. |
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
Conflicts have been resolved. A maintainer will review the pull request shortly. |
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.
Approved
) | ||
else: | ||
msg = ( | ||
_("File uploads are prohibited due to the list of acceptable file extensions being empty") |
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.
Interesting and a good catch. I'm not sure I would have thought of this case
[sc-5645]
Previously, when adding Files to a test, the API does not validate whether the title supplied is associated with a valid file extension. This fix validates the title of the 'files' object for a supported extension, and then return an error message if the file extension is not supported or does not exist.
This fix applies to the generic json parser and the finding/files, test/files and engagement/files endpoints.