- 
          
 - 
                Notifications
    
You must be signed in to change notification settings  - Fork 205
 
feat: implement message size validation to prevent excessive payloads #1197
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
Conversation
Added MAX_MESSAGE_LENGTH constant and implemented validation to ensure messages do not exceed the maximum allowed size in MobilePortStream and RemoteCommunicationPostMessageStream.
          Codecov ReportAll modified and coverable lines are covered by tests ✅ 
 Additional details and impacted files@@            Coverage Diff             @@
##             main    #1197      +/-   ##
==========================================
+ Coverage   74.02%   74.06%   +0.04%     
==========================================
  Files         182      182              
  Lines        4343     4350       +7     
  Branches     1064     1066       +2     
==========================================
+ Hits         3215     3222       +7     
  Misses       1128     1128              ☔ View full report in Codecov by Sentry.  | 
    
          
 | 
    
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.
LGTM



Description
Introduces a 1MB message size limit for communication streams to prevent potential memory issues and DoS attacks.
Changes
MAX_MESSAGE_LENGTHconstant (1MB) in configSecurity Impact
Prevents potential denial of service attacks and memory issues from oversized messages in communication channels.