Closed tkomlodi closed 11 months ago
Attention: 44 lines
in your changes are missing coverage. Please review.
Comparison is base (
a867b67
) 23.15% compared to head (b7adbc2
) 23.08%. Report is 1 commits behind head on master.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Thanks @tkomlodi for the PR and presenting Idea for fixing this issue.
As proposed earlier, I added a new level 10 endpoint to UnrestrictedFileUpload which accepts unlimited sized files. These files are stored in-memory on the heap to allow triggering an out-of-memory condition.
VulnerableAppConfiguration was updated to remove the default file size limit for the new endpoint only.
Two new maven dependencies were added:
I didn't add the new labels to the non-English i18n files. Let me know if that is required.
The unit test does not test the actual enforcement (or lack of) the file size limit. That could only be done with an integration test which I did not want to introduce. I manually tested that the limit is removed from the new endpoint but it still applies to all the other ones.
This change contains the prior fix for #449 (https://github.com/SasanLabs/VulnerableApp/pull/453). This is the only way I can run the application in my environment. I hope that, if that is merged first, it won't cause any issues. However, I'm not 100% sure how github will react.
Thanks!