Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1686582 - Incorrect handling of fragmented KeyUpdate messages
Summary: Incorrect handling of fragmented KeyUpdate messages
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gnutls
Version: 8.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.0
Assignee: Anderson Sasaki
QA Contact: BaseOS QE Security Team
Depends On:
TreeView+ depends on / blocked
Reported: 2019-03-07 18:26 UTC by Hubert Kario
Modified: 2019-04-15 16:30 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Gitlab gnutls/gnutls/issues/699 None None None 2019-03-07 18:28:07 UTC
Red Hat Bugzilla 1673975 None NEW gnutls does not support multiple KeyUpdate messages on a connection 2019-04-15 16:30:02 UTC

Internal Links: 1673975

Description Hubert Kario 2019-03-07 18:26:52 UTC
Description of problem:
KeyUpdate messages interleaved with ApplicationData are not rejected by gnutls. 
This is a RFC 8446 section 5.1 violation:

   -  Handshake messages MUST NOT be interleaved with other record
      types.  That is, if a handshake message is split over two or more
      records, there MUST NOT be any other records between them.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. run tlsfuzzer test script against gnutls server

Actual results:
among failing tests there are
  '1/4 fragmented keyupdate msg, appdata between'
  '2/3 fragmented keyupdate msg, appdata between'
  '3/2 fragmented keyupdate msg, appdata between'
  '4/1 fragmented keyupdate msg, appdata between'

Expected results:
the above tests should not be listed as failing

Additional info:
there are also issues in handling split GET messages and multiple KeyUpdates in succession, but they are not directly related to this issue

Note You need to log in before you can comment on or make changes to this bug.