Skip to content
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

fix(server): Enforce size limits on UE4 crash reports [ISSUE-1315] #1099

Merged
merged 3 commits into from
Oct 7, 2021

Conversation

jan-auer
Copy link
Member

@jan-auer jan-auer commented Oct 6, 2021

UE4 crash reports are compressed archives that are unpacked during ingestion in Relay. After expansion, the size of the resulting envelope and its file attachments was never checked, which could pass attachments far exceeding the maximum size limits.

Note that the current implementation drops the entire envelope if even a single attachment file exceeds the file size limit. I went with this approach because it is consistent to how the store endpoint behaves, reusing the same function. We may want to reconsider this, since in UE4 this is usually log files, which only have marginal value compared to the actual crash report. I suggest tackling this in a follow-up.

@jan-auer jan-auer requested a review from a team October 6, 2021 14:53
@jan-auer jan-auer self-assigned this Oct 6, 2021
@jan-auer jan-auer changed the title fix(server): Enforce size limits on UE4 crash reports fix(server): Enforce size limits on UE4 crash reports [ISSUE-1315] Oct 6, 2021
Copy link
Member

@jjbayer jjbayer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, should we add an integration test in test_unreal.py?

@jan-auer jan-auer merged commit c2daf43 into master Oct 7, 2021
@jan-auer jan-auer deleted the fix/ue4-size-limits branch October 7, 2021 11:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants