RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1686548 - Incorrect handling of fragmented KeyUpdate messages
Summary: Incorrect handling of fragmented KeyUpdate messages
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: openssl
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.0
Assignee: Tomas Mraz
QA Contact: Daiki Ueno
URL:
Whiteboard:
Depends On: 1643026 1682501
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-07 16:43 UTC by Alicja Kario
Modified: 2020-11-14 11:20 UTC (History)
1 user (show)

Fixed In Version: openssl-1.1.1b-3.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 22:40:19 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openssl openssl issues 8189 0 None closed Fragmented handshake messages with app data between them are not rejected 2020-12-15 12:00:01 UTC
Github openssl openssl pull 8191 0 None closed Don't interleave handshake and other record types in TLSv1.3 2020-12-15 12:00:02 UTC
Red Hat Product Errata RHSA-2019:3700 0 None None None 2019-11-05 22:40:43 UTC

Description Alicja Kario 2019-03-07 16:43:24 UTC
Description of problem:
When OpenSSL receives fragmented KeyUpdate message with application data in-between, it does not reject the connection. 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):
openssl-1.1.1-8.el8.x86_64

How reproducible:
always

Steps to Reproduce:
1. run tlsfuzzer test-tls13-keyupdate.py against openssl server

Actual results:
failed cases include
  '1/4 fragmented keyupdate msg, appdata between'
  '2/3 fragmented keyupdate msg, appdata between'
  '3/2 fragmented keyupdate msg, appdata between'

Expected results:
above mentioned tests pass

Additional info:
There are also two unrelated failures:
'app data split, conversation with KeyUpdate msg'
caused by https://github.com/openssl/openssl/issues/8188
'large KeyUpdate message'
caused by https://github.com/openssl/openssl/issues/8189 and https://github.com/openssl/openssl/issues/8293

Comment 4 Daiki Ueno 2019-07-04 11:24:48 UTC
Created attachment 1587363 [details]
test log

Successfully verified with openssl-1.1.1c-1.el8.x86_64.

Comment 6 errata-xmlrpc 2019-11-05 22:40:19 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:3700


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