mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 06:38:20 +00:00
ssl: Cap number of alerts parsed from SSL record
Limit the number of events raised from an SSL record with content_type alert (21) to a configurable maximum number (default 10). For TLS 1.3, the limit is set to 1 as specified in the RFC. Add a new weird cases where the limit is exceeded. OSS-Fuzz managed to generate a reproducer that raised ~660k ssl_plaintext and ssl_alert events given ~810kb of input data. This change prevents this with hopefully no negative side-effect in the real-world.
This commit is contained in:
parent
a5b94f04fd
commit
c960d279a2
4 changed files with 46 additions and 1 deletions
5
NEWS
5
NEWS
|
@ -187,6 +187,11 @@ Changed Functionality
|
|||
- The input framework now provides better information in error messages when
|
||||
encountering missing non-optional field while loading data.
|
||||
|
||||
- The SSL analyzer will now parse a configurable maximum of 10 SSL Alerts per
|
||||
SSL message. For TLS 1.3, the maximum is implicitly 1 as defined by RFC 8446.
|
||||
If there are more alerts, a new weird "SSL_excessive_alerts_in_record" is raised.
|
||||
For non-TLS 1.3, the maximum can be redefined via ``SSL::max_alerts_per_record``.
|
||||
|
||||
Deprecated Functionality
|
||||
------------------------
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue